Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b8220e9e8ca05e59ca47ba03ad4070f53d1c7dee50431e0f9117d09956399a9

Tx prefix hash: 9e814b867bb0bc5907d43ff03fde2b1b154a3b1d4cf32f4853873079cd3b7ef2
Tx public key: 6d4d3b6b824e043ceb91af96ae7a0831a2bbcfdbe8dd1640a4c89adb2189105b
Timestamp: 1752005009 Timestamp [UCT]: 2025-07-08 20:03:29 Age [y:d:h:m:s]: 00:127:17:57:20
Block: 1321520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89746 RingCT/type: yes/0
Extra: 016d4d3b6b824e043ceb91af96ae7a0831a2bbcfdbe8dd1640a4c89adb2189105b0211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1c03171c125d0bf5c32e71bad1a5263654bb2a56b84365617f1954417268b99 0.600000000000 1809227 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": 1321530, "vin": [ { "gen": { "height": 1321520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1c03171c125d0bf5c32e71bad1a5263654bb2a56b84365617f1954417268b99" } } ], "extra": [ 1, 109, 77, 59, 107, 130, 78, 4, 60, 235, 145, 175, 150, 174, 122, 8, 49, 162, 187, 207, 219, 232, 221, 22, 64, 164, 200, 154, 219, 33, 137, 16, 91, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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