Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64265fb6647ff3d6c5c08cabe503188e8bb82a1e5dd8508e7780496760f11c3b

Tx prefix hash: 68c8afff8ed6d9da05f3338e1fa87ce494197753da3d42305032d3b8f7ec05dc
Tx public key: 6706f0e6d375809cc24809a728b11afc7ba3a4f856681a311a3983b67e5252cc
Timestamp: 1746429965 Timestamp [UCT]: 2025-05-05 07:26:05 Age [y:d:h:m:s]: 00:194:21:07:21
Block: 1276145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136994 RingCT/type: yes/0
Extra: 016706f0e6d375809cc24809a728b11afc7ba3a4f856681a311a3983b67e5252cc0211000000079f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e5a51135421073fb6e8c3113fe621bcf8106f55f985e72a8b2b93643af4eb0d 0.600000000000 1763468 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": 1276155, "vin": [ { "gen": { "height": 1276145 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e5a51135421073fb6e8c3113fe621bcf8106f55f985e72a8b2b93643af4eb0d" } } ], "extra": [ 1, 103, 6, 240, 230, 211, 117, 128, 156, 194, 72, 9, 167, 40, 177, 26, 252, 123, 163, 164, 248, 86, 104, 26, 49, 26, 57, 131, 182, 126, 82, 82, 204, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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