Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e03415e9b204ed5c22cf21b2794a30676b80dbb36dac44eed23ae0548dfc9cb

Tx prefix hash: b2f585238c1271bf57e314df6431100faa1b728614658dc7bf66c2a11331116c
Tx public key: 551b019b7522168856e0c02bb0401045b8d2c219184f788ca3a52ea82f3cb6c4
Timestamp: 1749666032 Timestamp [UCT]: 2025-06-11 18:20:32 Age [y:d:h:m:s]: 00:151:09:51:41
Block: 1302931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105905 RingCT/type: yes/0
Extra: 01551b019b7522168856e0c02bb0401045b8d2c219184f788ca3a52ea82f3cb6c4021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83acc6b9910abbda796439515d698edebdd8c8e9ec5d5f8daa16799d4c6c9777 0.600000000000 1790506 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": 1302941, "vin": [ { "gen": { "height": 1302931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83acc6b9910abbda796439515d698edebdd8c8e9ec5d5f8daa16799d4c6c9777" } } ], "extra": [ 1, 85, 27, 1, 155, 117, 34, 22, 136, 86, 224, 192, 43, 176, 64, 16, 69, 184, 210, 194, 25, 24, 79, 120, 140, 163, 165, 46, 168, 47, 60, 182, 196, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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