Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ccee7a9c3c24e4084d36258ce21e4e5d33e19e6f70fe48be2aad8c513c03ca8

Tx prefix hash: 0b85e180d9e85108e21b31eb1210b09f7ceab07bf1b21190635b82156169a71b
Tx public key: bf5ad6c997dadf9e3b9b59a136da0bd26c44231e24cd87c97daa795d84b497f3
Timestamp: 1707725797 Timestamp [UCT]: 2024-02-12 08:16:37 Age [y:d:h:m:s]: 00:314:01:40:45
Block: 955795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224883 RingCT/type: yes/0
Extra: 01bf5ad6c997dadf9e3b9b59a136da0bd26c44231e24cd87c97daa795d84b497f30211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a49563be0d9956713192147c0fde0a406cc316294d5b7bce9afaa327a3ea0d9 0.600000000000 1415095 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": 955805, "vin": [ { "gen": { "height": 955795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a49563be0d9956713192147c0fde0a406cc316294d5b7bce9afaa327a3ea0d9" } } ], "extra": [ 1, 191, 90, 214, 201, 151, 218, 223, 158, 59, 155, 89, 161, 54, 218, 11, 210, 108, 68, 35, 30, 36, 205, 135, 201, 125, 170, 121, 93, 132, 180, 151, 243, 2, 17, 0, 0, 0, 5, 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