Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80c29ade8a88076f518b66e4becb81db0cea5e200590799d722ad87b13f75b6f

Tx prefix hash: 363cbe3bf34d8f87d72ababa9bc1737220692063e403774575ffe48467750a9c
Tx public key: 6ffd2620117aa59cb202b9e16d658bdea46e76d8338030de7b5fba46b6e55c1c
Timestamp: 1582035685 Timestamp [UCT]: 2020-02-18 14:21:25 Age [y:d:h:m:s]: 05:233:18:32:29
Block: 67518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1317813 RingCT/type: yes/0
Extra: 016ffd2620117aa59cb202b9e16d658bdea46e76d8338030de7b5fba46b6e55c1c02110000000403d36d11000000000000000000

1 output(s) for total of 366.678668170000 dcy

stealth address amount amount idx
00: 3f187c3029f2ad7490b9f070418e627a620514a06fb1c4d12e5c5c00d751d101 366.678668170000 124381 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": 67528, "vin": [ { "gen": { "height": 67518 } } ], "vout": [ { "amount": 366678668170, "target": { "key": "3f187c3029f2ad7490b9f070418e627a620514a06fb1c4d12e5c5c00d751d101" } } ], "extra": [ 1, 111, 253, 38, 32, 17, 122, 165, 156, 178, 2, 185, 225, 109, 101, 139, 222, 164, 110, 118, 216, 51, 128, 48, 222, 123, 95, 186, 70, 182, 229, 92, 28, 2, 17, 0, 0, 0, 4, 3, 211, 109, 17, 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