Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f3ca9eb36a5cd8a7faf04437fd638c7f6a53252ba23f7562689c2828e429d11

Tx prefix hash: 38063b8be1d59bf55d8ef8c649c1ba2277c261edd02e1487c2b5697ec54988ca
Tx public key: 59ce0bf368a5a5d49916bf5a14a0a0b88ff9a2f2fd0959735c60242fab85bb9f
Timestamp: 1734897893 Timestamp [UCT]: 2024-12-22 20:04:53 Age [y:d:h:m:s]: 00:097:01:55:35
Block: 1180979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69141 RingCT/type: yes/0
Extra: 0159ce0bf368a5a5d49916bf5a14a0a0b88ff9a2f2fd0959735c60242fab85bb9f0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2caf448dc3243c6d50c36e659713e1086bcf23d7136ac70f00901b784783b560 0.600000000000 1667394 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": 1180989, "vin": [ { "gen": { "height": 1180979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2caf448dc3243c6d50c36e659713e1086bcf23d7136ac70f00901b784783b560" } } ], "extra": [ 1, 89, 206, 11, 243, 104, 165, 165, 212, 153, 22, 191, 90, 20, 160, 160, 184, 143, 249, 162, 242, 253, 9, 89, 115, 92, 96, 36, 47, 171, 133, 187, 159, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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