Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb00ce2b7709c99db9f8b630d28f16c34bccc64d0816615b1e6cbce027e8e610

Tx prefix hash: 6519d54719fe7a9ab02f0190d57c8f7168d3abe0cd9be276b0951baf26ae6d9e
Tx public key: e07ceb1d5e43892ead8c22a2a802e5ab1ceb3767c2f3dfef483eeedfe75d17a1
Timestamp: 1732768315 Timestamp [UCT]: 2024-11-28 04:31:55 Age [y:d:h:m:s]: 00:140:20:55:58
Block: 1163313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100492 RingCT/type: yes/0
Extra: 01e07ceb1d5e43892ead8c22a2a802e5ab1ceb3767c2f3dfef483eeedfe75d17a10211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b3dc7b8b821bd1ad66a57afecec6f22c0ae82b021bfef9ad44a4a51b416f84e 0.600000000000 1648980 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": 1163323, "vin": [ { "gen": { "height": 1163313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b3dc7b8b821bd1ad66a57afecec6f22c0ae82b021bfef9ad44a4a51b416f84e" } } ], "extra": [ 1, 224, 124, 235, 29, 94, 67, 137, 46, 173, 140, 34, 162, 168, 2, 229, 171, 28, 235, 55, 103, 194, 243, 223, 239, 72, 62, 238, 223, 231, 93, 23, 161, 2, 17, 0, 0, 0, 3, 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