Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11b454ef0c83ea5362efaa513fd3301cd620bdbb1d03232aca9c69e92df70bdf

Tx prefix hash: 6bdf4510b83630f47f1bae6998de066b2ada141019299a6ed716ed6ae9dd64a7
Tx public key: 7877a5993d4a6293593dd5e6c410354c9b10fc918723eacde9b4ab3cb3fb5936
Timestamp: 1718584558 Timestamp [UCT]: 2024-06-17 00:35:58 Age [y:d:h:m:s]: 00:221:04:51:34
Block: 1045832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158234 RingCT/type: yes/0
Extra: 017877a5993d4a6293593dd5e6c410354c9b10fc918723eacde9b4ab3cb3fb593602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3dbea777f32985d85b2911c98178f6ef3e4d2382679410cc6a4a69c036811742 0.600000000000 1515519 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": 1045842, "vin": [ { "gen": { "height": 1045832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3dbea777f32985d85b2911c98178f6ef3e4d2382679410cc6a4a69c036811742" } } ], "extra": [ 1, 120, 119, 165, 153, 61, 74, 98, 147, 89, 61, 213, 230, 196, 16, 53, 76, 155, 16, 252, 145, 135, 35, 234, 205, 233, 180, 171, 60, 179, 251, 89, 54, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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