Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7cad8000de358f830c192bd4af2388afaee6386579bca48b7be76c08571ef1c

Tx prefix hash: ec222c162cf9faf4bc36afb63d3861951c15a1edf622dbdf3727feaf7f3299fb
Tx public key: 4742f7c2311c4ee5dcb6eaaac5fc06abbae4ca1200c6f0b711840ce5db15fe2c
Timestamp: 1695745009 Timestamp [UCT]: 2023-09-26 16:16:49 Age [y:d:h:m:s]: 01:241:21:05:24
Block: 856668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433981 RingCT/type: yes/0
Extra: 014742f7c2311c4ee5dcb6eaaac5fc06abbae4ca1200c6f0b711840ce5db15fe2c021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.890232291000 dcy

stealth address amount amount idx
00: 9ab938df4d9e93acae57b8535056a35f669bcbed8288bbf176e5ac544508ae41 0.890232291000 1310750 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": 856678, "vin": [ { "gen": { "height": 856668 } } ], "vout": [ { "amount": 890232291, "target": { "key": "9ab938df4d9e93acae57b8535056a35f669bcbed8288bbf176e5ac544508ae41" } } ], "extra": [ 1, 71, 66, 247, 194, 49, 28, 78, 229, 220, 182, 234, 170, 197, 252, 6, 171, 186, 228, 202, 18, 0, 198, 240, 183, 17, 132, 12, 229, 219, 21, 254, 44, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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