Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0fe79bce03e7c879ea3c7b17cb2116f84b426e4458ad88100f03937be4d297f7

Tx prefix hash: 453dd3cb4fe5d0b1a7370a49ce21827e034131e125212fed03ad1253d51faa68
Tx public key: 16f2e0f1b29ca97f428fd2292337574ab3ebb565052bcf3c94d21a1afa09e7ef
Timestamp: 1705690470 Timestamp [UCT]: 2024-01-19 18:54:30 Age [y:d:h:m:s]: 00:357:08:22:10
Block: 938894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255850 RingCT/type: yes/0
Extra: 0116f2e0f1b29ca97f428fd2292337574ab3ebb565052bcf3c94d21a1afa09e7ef02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57e7e477f85bc10bcd8da00dfbbf5e4eccf190e1c5507a3871c9d1ef3b8e88de 0.600000000000 1396976 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 938904, "vin": [ { "gen": { "height": 938894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57e7e477f85bc10bcd8da00dfbbf5e4eccf190e1c5507a3871c9d1ef3b8e88de" } } ], "extra": [ 1, 22, 242, 224, 241, 178, 156, 169, 127, 66, 143, 210, 41, 35, 55, 87, 74, 179, 235, 181, 101, 5, 43, 207, 60, 148, 210, 26, 26, 250, 9, 231, 239, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8