Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f5a02d24317a6d83b50280abd58956da73ef1dfa1b57c7e9223a3e684ebc988

Tx prefix hash: e95763fce41858cfa2ab436a0a0388e2537af1b603b2e056b2ee1ff3ab3dea14
Tx public key: d9ae914cc31c3dfbdd1609e5d8746a6dc23aff727bfb8d0debff296d2e7ec2af
Timestamp: 1699251698 Timestamp [UCT]: 2023-11-06 06:21:38 Age [y:d:h:m:s]: 01:154:12:10:34
Block: 885542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371616 RingCT/type: yes/0
Extra: 01d9ae914cc31c3dfbdd1609e5d8746a6dc23aff727bfb8d0debff296d2e7ec2af0211000000024b8f5122000000000000000000

1 output(s) for total of 0.714219581000 dcy

stealth address amount amount idx
00: 3b7e653c3d9c73f459c31ed10f1145def4d8e27aaf6f54a2e8a93fd681c273ec 0.714219581000 1341319 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": 885552, "vin": [ { "gen": { "height": 885542 } } ], "vout": [ { "amount": 714219581, "target": { "key": "3b7e653c3d9c73f459c31ed10f1145def4d8e27aaf6f54a2e8a93fd681c273ec" } } ], "extra": [ 1, 217, 174, 145, 76, 195, 28, 61, 251, 221, 22, 9, 229, 216, 116, 106, 109, 194, 58, 255, 114, 123, 251, 141, 13, 235, 255, 41, 109, 46, 126, 194, 175, 2, 17, 0, 0, 0, 2, 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