Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40d664c0e2eed2f539fd85cbdea83430a49c062fce8d7fb5828581a904a7d27f

Tx prefix hash: c3bba91d235771fee4136d013a3409b1652df408047a5c8c9da9ebd06f245ad6
Tx public key: f90ff2ef6d6f6c066ae3538b2096dcd31cac9e69295208df9de04a47b02bff4f
Timestamp: 1626741734 Timestamp [UCT]: 2021-07-20 00:42:14 Age [y:d:h:m:s]: 03:129:23:04:35
Block: 297240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 864497 RingCT/type: yes/0
Extra: 01f90ff2ef6d6f6c066ae3538b2096dcd31cac9e69295208df9de04a47b02bff4f021100000001c97064b9000000000000000000

1 output(s) for total of 63.550794493000 dcy

stealth address amount amount idx
00: e50aeb8b67fd5a711a506876a180e737c7c720ac0f176856d2feac48310f19e5 63.550794493000 622152 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": 297250, "vin": [ { "gen": { "height": 297240 } } ], "vout": [ { "amount": 63550794493, "target": { "key": "e50aeb8b67fd5a711a506876a180e737c7c720ac0f176856d2feac48310f19e5" } } ], "extra": [ 1, 249, 15, 242, 239, 109, 111, 108, 6, 106, 227, 83, 139, 32, 150, 220, 211, 28, 172, 158, 105, 41, 82, 8, 223, 157, 224, 74, 71, 176, 43, 255, 79, 2, 17, 0, 0, 0, 1, 201, 112, 100, 185, 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