Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84851a8a0171fc9c99c1c7f238245d946ea6ada08c9019419d3ffd5e01bad81a

Tx prefix hash: 636f4f84887c7198888b9eb07729e8744a5faed18bd2694f6e885f5f291686da
Tx public key: 7db1da855708d34795a470ffcb57d814f597d64255fbdb65c7c309cc9638d023
Timestamp: 1581378481 Timestamp [UCT]: 2020-02-10 23:48:01 Age [y:d:h:m:s]: 04:326:00:08:14
Block: 62453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125042 RingCT/type: yes/0
Extra: 017db1da855708d34795a470ffcb57d814f597d64255fbdb65c7c309cc9638d02302110000000e4ac5aa02000000000000000000

1 output(s) for total of 381.132171735000 dcy

stealth address amount amount idx
00: e07d4c66ff4d56b5aab3b8eccec78aabe6f3a8414b937606049bee6860fa1912 381.132171735000 115213 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": 62463, "vin": [ { "gen": { "height": 62453 } } ], "vout": [ { "amount": 381132171735, "target": { "key": "e07d4c66ff4d56b5aab3b8eccec78aabe6f3a8414b937606049bee6860fa1912" } } ], "extra": [ 1, 125, 177, 218, 133, 87, 8, 211, 71, 149, 164, 112, 255, 203, 87, 216, 20, 245, 151, 214, 66, 85, 251, 219, 101, 199, 195, 9, 204, 150, 56, 208, 35, 2, 17, 0, 0, 0, 14, 74, 197, 170, 2, 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