Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cc03172cce96a0faf492d9ca28811d5b38ee38e0fbe32adf575f4807f1f6b6b

Tx prefix hash: 99936c265335279e2d342c2745176e9be2c5c18322757654ec733abc22467f44
Tx public key: 954e78e09e6ce2c30713774f7d880d41dd78a237a35262a97428d6b24bbde47a
Timestamp: 1724972860 Timestamp [UCT]: 2024-08-29 23:07:40 Age [y:d:h:m:s]: 00:087:00:08:50
Block: 1098773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62235 RingCT/type: yes/0
Extra: 01954e78e09e6ce2c30713774f7d880d41dd78a237a35262a97428d6b24bbde47a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf086d92d3c515ccc732b3d9ccfd8c8cbb06af5fb2748a9b0be0bdf03025f795 0.600000000000 1574604 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": 1098783, "vin": [ { "gen": { "height": 1098773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf086d92d3c515ccc732b3d9ccfd8c8cbb06af5fb2748a9b0be0bdf03025f795" } } ], "extra": [ 1, 149, 78, 120, 224, 158, 108, 226, 195, 7, 19, 119, 79, 125, 136, 13, 65, 221, 120, 162, 55, 163, 82, 98, 169, 116, 40, 214, 178, 75, 189, 228, 122, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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