Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4646f99ad4c7ab45541d84c4d1ad87455f57c6fcf4ba6c506a9106097a916753

Tx prefix hash: 4c5d6b8be8921e60d3a29bb25cfb050b419bba46dbda74078738711c0b941fae
Tx public key: a28645e5d41c0abd68305d7dd0c5c4b715101dfaf7c35ecd472cd2a1d3f6b759
Timestamp: 1749768747 Timestamp [UCT]: 2025-06-12 22:52:27 Age [y:d:h:m:s]: 00:149:20:46:53
Block: 1303756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104827 RingCT/type: yes/0
Extra: 01a28645e5d41c0abd68305d7dd0c5c4b715101dfaf7c35ecd472cd2a1d3f6b759021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b587dde01c6dc40426ce0564049511cb6922e936617f18db818ebfc954baaf91 0.600000000000 1791339 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": 1303766, "vin": [ { "gen": { "height": 1303756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b587dde01c6dc40426ce0564049511cb6922e936617f18db818ebfc954baaf91" } } ], "extra": [ 1, 162, 134, 69, 229, 212, 28, 10, 189, 104, 48, 93, 125, 208, 197, 196, 183, 21, 16, 29, 250, 247, 195, 94, 205, 71, 44, 210, 161, 211, 246, 183, 89, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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