Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bef7e6c994ba15861d57509ec4df6aeec4a98783312277e7160fa76c0d6f028e

Tx prefix hash: 27c368d0b771bad43d8d7036abd10a979596c74147b786f9e3bbeae9d02d97f5
Tx public key: 369d55fbf5c617153a68fab7cfd779753c8b59516c8339d65be266bf50f99df3
Timestamp: 1705602927 Timestamp [UCT]: 2024-01-18 18:35:27 Age [y:d:h:m:s]: 01:090:11:19:33
Block: 938177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325767 RingCT/type: yes/0
Extra: 01369d55fbf5c617153a68fab7cfd779753c8b59516c8339d65be266bf50f99df30211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86f8ededa10b91644338df9cf3eb446a1067d5dc9708c2963f1ed08a41b342df 0.600000000000 1396245 of 15

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": 938187, "vin": [ { "gen": { "height": 938177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86f8ededa10b91644338df9cf3eb446a1067d5dc9708c2963f1ed08a41b342df" } } ], "extra": [ 1, 54, 157, 85, 251, 245, 198, 23, 21, 58, 104, 250, 183, 207, 215, 121, 117, 60, 139, 89, 81, 108, 131, 57, 214, 91, 226, 102, 191, 80, 249, 157, 243, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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