Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccb9ca7c7d8684940160f402f4beb39a8ea65e8689f17e6a59943c75e304306d

Tx prefix hash: 450ec9efb78303e35341d324640fc3640e6242568f2f7a61a05f60167db4ac63
Tx public key: 87365b63b2f791f1e446a02293256ff268b8eedfb70d5cd6f194a039fa497a7f
Timestamp: 1707936639 Timestamp [UCT]: 2024-02-14 18:50:39 Age [y:d:h:m:s]: 01:010:15:21:21
Block: 957535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268614 RingCT/type: yes/0
Extra: 0187365b63b2f791f1e446a02293256ff268b8eedfb70d5cd6f194a039fa497a7f0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 585c854e7e522db9ab997e7813cc33843318824a43af8e23b14ce6f026f01ad9 0.600000000000 1416853 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": 957545, "vin": [ { "gen": { "height": 957535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "585c854e7e522db9ab997e7813cc33843318824a43af8e23b14ce6f026f01ad9" } } ], "extra": [ 1, 135, 54, 91, 99, 178, 247, 145, 241, 228, 70, 160, 34, 147, 37, 111, 242, 104, 184, 238, 223, 183, 13, 92, 214, 241, 148, 160, 57, 250, 73, 122, 127, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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