Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4cd47bdc562849e1996d0d07004afb1f221a8bd9917101db3bfe5ac232d87f8

Tx prefix hash: aeeb7c6354a5ee8ef5013732bfc1d2da6e8eb63e58e0c8df66c81d5fa9727cba
Tx public key: fa25568b7d96fa3d95fd67aa9b3c4fbc9f29e0fbb866ae6b134ace5aa31569af
Timestamp: 1733080512 Timestamp [UCT]: 2024-12-01 19:15:12 Age [y:d:h:m:s]: 00:113:01:11:13
Block: 1165905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80582 RingCT/type: yes/0
Extra: 01fa25568b7d96fa3d95fd67aa9b3c4fbc9f29e0fbb866ae6b134ace5aa31569af02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1aa1ebd3d1f1aa3dc5c18cb06743c089ec84c33d7bf7f6be59bf92e46b9ec5e1 0.600000000000 1651580 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": 1165915, "vin": [ { "gen": { "height": 1165905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aa1ebd3d1f1aa3dc5c18cb06743c089ec84c33d7bf7f6be59bf92e46b9ec5e1" } } ], "extra": [ 1, 250, 37, 86, 139, 125, 150, 250, 61, 149, 253, 103, 170, 155, 60, 79, 188, 159, 41, 224, 251, 184, 102, 174, 107, 19, 74, 206, 90, 163, 21, 105, 175, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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