Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0389b0131c6bf7838e18fa23229b19919ffe9b6bed0588a4528d7fa2c7fc3238

Tx prefix hash: 5f9229d793f6707f9267dd0eb2acdfcb29c8ea01b3fd83de52ac9b90e963700b
Tx public key: eb8dd9c3735db5dce9d20c7b12b84b6b39bbf29a35086cf36a56bdc3d94b3f87
Timestamp: 1703462168 Timestamp [UCT]: 2023-12-24 23:56:08 Age [y:d:h:m:s]: 01:133:12:06:46
Block: 920460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356540 RingCT/type: yes/0
Extra: 01eb8dd9c3735db5dce9d20c7b12b84b6b39bbf29a35086cf36a56bdc3d94b3f8702110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fd37dd271995561f252a73848eeb5bf837aba4fc0b3642218adbc65e8fefd78 0.600000000000 1378138 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": 920470, "vin": [ { "gen": { "height": 920460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fd37dd271995561f252a73848eeb5bf837aba4fc0b3642218adbc65e8fefd78" } } ], "extra": [ 1, 235, 141, 217, 195, 115, 93, 181, 220, 233, 210, 12, 123, 18, 184, 75, 107, 57, 187, 242, 154, 53, 8, 108, 243, 106, 86, 189, 195, 217, 75, 63, 135, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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