Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 164d03c0d6ddf39f8cce533d42ea60b8b43189e91c31a671ab2f601f9fd1e59b

Tx prefix hash: 09764c1ba20bcab3f702e3f9775ab8771d4a57558d05e1413e8ee81e4830a9e4
Tx public key: 8efd0bccebe9f3c797274e198fe3d721819aa234390dbe3460d1847b10cfd657
Timestamp: 1761310528 Timestamp [UCT]: 2025-10-24 12:55:28 Age [y:d:h:m:s]: 00:034:10:58:30
Block: 1396928 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24668 RingCT/type: yes/0
Extra: 018efd0bccebe9f3c797274e198fe3d721819aa234390dbe3460d1847b10cfd6570211000000015dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44f4f8475261c51c94e57f78f8394bd685fc1a361d7340dc52b1c9a1d8a47579 0.600000000000 1885217 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": 1396938, "vin": [ { "gen": { "height": 1396928 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44f4f8475261c51c94e57f78f8394bd685fc1a361d7340dc52b1c9a1d8a47579" } } ], "extra": [ 1, 142, 253, 11, 204, 235, 233, 243, 199, 151, 39, 78, 25, 143, 227, 215, 33, 129, 154, 162, 52, 57, 13, 190, 52, 96, 209, 132, 123, 16, 207, 214, 87, 2, 17, 0, 0, 0, 1, 93, 251, 190, 42, 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