Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e389f9b1918b232f851efa20e50ac22dc617915fbcde1d6b6e76cf6cc0b9f3d2

Tx prefix hash: da789e17a455c69dc85c156b8aa341cc60e5e72f487150cecc000b3add8c21f3
Tx public key: 0e06ef2c8f37613300060002c97629b1aacdc35bab9324624973acabfc78c4cf
Timestamp: 1696882811 Timestamp [UCT]: 2023-10-09 20:20:11 Age [y:d:h:m:s]: 01:198:00:17:01
Block: 866112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402565 RingCT/type: yes/0
Extra: 010e06ef2c8f37613300060002c97629b1aacdc35bab9324624973acabfc78c4cf0211000000034b8f5122000000000000000000

1 output(s) for total of 0.828345347000 dcy

stealth address amount amount idx
00: 8407b9e49e87d142ec9b05a6d6789d14674de78de5acf4bdb4127272cc410f1f 0.828345347000 1320682 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": 866122, "vin": [ { "gen": { "height": 866112 } } ], "vout": [ { "amount": 828345347, "target": { "key": "8407b9e49e87d142ec9b05a6d6789d14674de78de5acf4bdb4127272cc410f1f" } } ], "extra": [ 1, 14, 6, 239, 44, 143, 55, 97, 51, 0, 6, 0, 2, 201, 118, 41, 177, 170, 205, 195, 91, 171, 147, 36, 98, 73, 115, 172, 171, 252, 120, 196, 207, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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