Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bbcaee62eb9d10bd431bca4a0c44ace89f303a5290c069bcf1d27871da19890

Tx prefix hash: 26a0498e652cae37a8071d8bb95bcf29aa0ac1bb15b6d37ea72dc2142b0135cf
Tx public key: 556f86577c6dc85fff17cb316f00d1bdbef0db8e8828803b2b87148d0390e7ca
Timestamp: 1756124063 Timestamp [UCT]: 2025-08-25 12:14:23 Age [y:d:h:m:s]: 00:136:01:58:23
Block: 1354114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97267 RingCT/type: yes/0
Extra: 01556f86577c6dc85fff17cb316f00d1bdbef0db8e8828803b2b87148d0390e7ca0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86078964e6b8f2f156d601300e7b10828789cac28e7614df7fd1c18292aa73c3 0.600000000000 1842095 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": 1354124, "vin": [ { "gen": { "height": 1354114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86078964e6b8f2f156d601300e7b10828789cac28e7614df7fd1c18292aa73c3" } } ], "extra": [ 1, 85, 111, 134, 87, 124, 109, 200, 95, 255, 23, 203, 49, 111, 0, 209, 189, 190, 240, 219, 142, 136, 40, 128, 59, 43, 135, 20, 141, 3, 144, 231, 202, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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