Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee09d1b687af3d030133958368eed10b7d08335cbfca4af204b89dea0206982e

Tx prefix hash: 54c20d436389facb90c201de7d25e5c6b90e478c27868a012592567e8289b729
Tx public key: bc4766bd13e10eb5ff46b7bf4fe91952047d96d2f73fbd077aa3b0e20fc1f06c
Timestamp: 1698682454 Timestamp [UCT]: 2023-10-30 16:14:14 Age [y:d:h:m:s]: 01:086:08:29:30
Block: 881043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322891 RingCT/type: yes/0
Extra: 01bc4766bd13e10eb5ff46b7bf4fe91952047d96d2f73fbd077aa3b0e20fc1f06c021100000012faf35c9c000000000000000000

1 output(s) for total of 0.739160608000 dcy

stealth address amount amount idx
00: e9d79fa918b6abf171e6731bcbc63d179993c9de675d6cf1b5bea8ecfc978b17 0.739160608000 1336613 of 0

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": 881053, "vin": [ { "gen": { "height": 881043 } } ], "vout": [ { "amount": 739160608, "target": { "key": "e9d79fa918b6abf171e6731bcbc63d179993c9de675d6cf1b5bea8ecfc978b17" } } ], "extra": [ 1, 188, 71, 102, 189, 19, 225, 14, 181, 255, 70, 183, 191, 79, 233, 25, 82, 4, 125, 150, 210, 247, 63, 189, 7, 122, 163, 176, 226, 15, 193, 240, 108, 2, 17, 0, 0, 0, 18, 250, 243, 92, 156, 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