Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21c39f4f1fb5415333f29775ca16005d3e527f72a18993437e7468d684d94391

Tx prefix hash: 5761febb163af620fb566b5de26e80ad7df151621b9baa4a775e262b392baf4f
Tx public key: a29f48917488f859e8c151423d6568f335da5acec5ba2c429cc02ed9fb97dfce
Timestamp: 1644710237 Timestamp [UCT]: 2022-02-12 23:57:17 Age [y:d:h:m:s]: 02:346:08:19:42
Block: 437347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 766812 RingCT/type: yes/0
Extra: 01a29f48917488f859e8c151423d6568f335da5acec5ba2c429cc02ed9fb97dfce021100000016d3fcec30000000000000000000

1 output(s) for total of 21.821677592000 dcy

stealth address amount amount idx
00: f95ef74608edff9511b656e5070ed84e49d9ffcaa024b8e8df89ec4e7c1fd5bb 21.821677592000 848950 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": 437357, "vin": [ { "gen": { "height": 437347 } } ], "vout": [ { "amount": 21821677592, "target": { "key": "f95ef74608edff9511b656e5070ed84e49d9ffcaa024b8e8df89ec4e7c1fd5bb" } } ], "extra": [ 1, 162, 159, 72, 145, 116, 136, 248, 89, 232, 193, 81, 66, 61, 101, 104, 243, 53, 218, 90, 206, 197, 186, 44, 66, 156, 192, 46, 217, 251, 151, 223, 206, 2, 17, 0, 0, 0, 22, 211, 252, 236, 48, 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