Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d01f86bb8e31727a5b8dc14d418bd7fcc3ec2754fae79dce05a6d8a838bd821d

Tx prefix hash: 2be82ee5307ac8e9418d2a7a87d77b4d691f1187d9afe860875a4fae2714a2c9
Tx public key: ac2b6aae628b9732546cef06fcc3d84ea3bbe2dfe3d5ba61a853d11cb073ffaa
Timestamp: 1617090900 Timestamp [UCT]: 2021-03-30 07:55:00 Age [y:d:h:m:s]: 03:241:12:27:17
Block: 229569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 932064 RingCT/type: yes/0
Extra: 01ac2b6aae628b9732546cef06fcc3d84ea3bbe2dfe3d5ba61a853d11cb073ffaa0211000000330dc70aa7000000000000000000

1 output(s) for total of 106.498425379000 dcy

stealth address amount amount idx
00: f2b8b1d43d33094a7c72eda6636232348ad420556656bfd642a14f3860414a63 106.498425379000 476367 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": 229579, "vin": [ { "gen": { "height": 229569 } } ], "vout": [ { "amount": 106498425379, "target": { "key": "f2b8b1d43d33094a7c72eda6636232348ad420556656bfd642a14f3860414a63" } } ], "extra": [ 1, 172, 43, 106, 174, 98, 139, 151, 50, 84, 108, 239, 6, 252, 195, 216, 78, 163, 187, 226, 223, 227, 213, 186, 97, 168, 83, 209, 28, 176, 115, 255, 170, 2, 17, 0, 0, 0, 51, 13, 199, 10, 167, 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