Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66327d844020a2a749d32a90936b8e777eac334306deb2bdf5bf556ae992354d

Tx prefix hash: be4f0c12f697d1d466eaacb6f85a7680105410fe4275339585cb0bcfcd5a9c6e
Tx public key: f01cb48a27182c76c8b87e2cb608c96850d9456a0905e241b3141a11b39cdd5d
Timestamp: 1745472691 Timestamp [UCT]: 2025-04-24 05:31:31 Age [y:d:h:m:s]: 00:210:16:55:13
Block: 1268224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148306 RingCT/type: yes/0
Extra: 01f01cb48a27182c76c8b87e2cb608c96850d9456a0905e241b3141a11b39cdd5d0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 492f600bd3ffbea2f0441168697e8e6e26babd0540bf36226b33bba919493ea1 0.600000000000 1755453 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": 1268234, "vin": [ { "gen": { "height": 1268224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "492f600bd3ffbea2f0441168697e8e6e26babd0540bf36226b33bba919493ea1" } } ], "extra": [ 1, 240, 28, 180, 138, 39, 24, 44, 118, 200, 184, 126, 44, 182, 8, 201, 104, 80, 217, 69, 106, 9, 5, 226, 65, 179, 20, 26, 17, 179, 156, 221, 93, 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