Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ec65ea2f84d01c5399f252bb4e9bbfca322c22549e30180bcb59d124222339f

Tx prefix hash: 71879e664c4b07e6e12983ff583f9433c950cf705c9088e27c4dc809d17ed29c
Tx public key: 648aa5159c5e6646ee4f3bf960321511b18dc0c1021fc861663ed3b1edce2b3a
Timestamp: 1725601992 Timestamp [UCT]: 2024-09-06 05:53:12 Age [y:d:h:m:s]: 00:079:00:11:54
Block: 1104003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56488 RingCT/type: yes/0
Extra: 01648aa5159c5e6646ee4f3bf960321511b18dc0c1021fc861663ed3b1edce2b3a021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: edea471f99e4901c6c3ba19d51e886811975f2fba0d4824a7bea93d821e3dc72 0.600000000000 1581050 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": 1104013, "vin": [ { "gen": { "height": 1104003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edea471f99e4901c6c3ba19d51e886811975f2fba0d4824a7bea93d821e3dc72" } } ], "extra": [ 1, 100, 138, 165, 21, 156, 94, 102, 70, 238, 79, 59, 249, 96, 50, 21, 17, 177, 141, 192, 193, 2, 31, 200, 97, 102, 62, 211, 177, 237, 206, 43, 58, 2, 17, 0, 0, 0, 8, 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