Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f611217220ff2f36b1c1242b1a792a8a5a6e5293b3b7d0371c6c68146374ea5

Tx prefix hash: eab02b41eb3a2b59c7a6ea9035cf803078a727a14d6069c5a7b6e64e45de9441
Tx public key: 6587abc6dc08456ccfbf02e2d903c3e044283dc89ee4f66a7001ff8fb20e618a
Timestamp: 1715468802 Timestamp [UCT]: 2024-05-11 23:06:42 Age [y:d:h:m:s]: 00:312:19:50:34
Block: 1020017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223591 RingCT/type: yes/0
Extra: 016587abc6dc08456ccfbf02e2d903c3e044283dc89ee4f66a7001ff8fb20e618a02110000000241ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9edf4a3c2ad21a8e887f0970c6080394593ee208967c8434c0710b2730207cee 0.600000000000 1484076 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": 1020027, "vin": [ { "gen": { "height": 1020017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9edf4a3c2ad21a8e887f0970c6080394593ee208967c8434c0710b2730207cee" } } ], "extra": [ 1, 101, 135, 171, 198, 220, 8, 69, 108, 207, 191, 2, 226, 217, 3, 195, 224, 68, 40, 61, 200, 158, 228, 246, 106, 112, 1, 255, 143, 178, 14, 97, 138, 2, 17, 0, 0, 0, 2, 65, 238, 28, 155, 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