Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26432ae643b4c85d7034af50dbfc66edc09b9aaf3f2da7de24835805db6b9ca4

Tx prefix hash: a3a1e25590f62861053cc6baa641ab6db643bfaf20afde9e7973f330a5970bd6
Tx public key: 667c8c520b94b8fceaaa3cfa20d0c30d03b2dbfc8c1435fbf4a4c835034199de
Timestamp: 1583857489 Timestamp [UCT]: 2020-03-10 16:24:49 Age [y:d:h:m:s]: 05:090:08:12:14
Block: 79978 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1220291 RingCT/type: yes/0
Extra: 01667c8c520b94b8fceaaa3cfa20d0c30d03b2dbfc8c1435fbf4a4c835034199de021100000004a08fd034000000000000000000

1 output(s) for total of 333.426777850000 dcy

stealth address amount amount idx
00: 4cc1a2b85fb2886f4a1a70c703f9132fbf9f6f13b1c0ec1f3a93bbc33d3b833f 333.426777850000 146342 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": 79988, "vin": [ { "gen": { "height": 79978 } } ], "vout": [ { "amount": 333426777850, "target": { "key": "4cc1a2b85fb2886f4a1a70c703f9132fbf9f6f13b1c0ec1f3a93bbc33d3b833f" } } ], "extra": [ 1, 102, 124, 140, 82, 11, 148, 184, 252, 234, 170, 60, 250, 32, 208, 195, 13, 3, 178, 219, 252, 140, 20, 53, 251, 244, 164, 200, 53, 3, 65, 153, 222, 2, 17, 0, 0, 0, 4, 160, 143, 208, 52, 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