Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f00377b07148892310b14b5a263c5bba68c9ebe21f6a4217c2f206696b0acf49

Tx prefix hash: 4dfe59c12ac42cd60f1cebf43e3dc36493da82ac2755aecf87569eb5b6a6ef69
Tx public key: cee186d9ffe5f221aa9b784d9d809278d266dee5935b195fd1de8a14aa8554af
Timestamp: 1704260070 Timestamp [UCT]: 2024-01-03 05:34:30 Age [y:d:h:m:s]: 01:055:04:39:49
Block: 927050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300529 RingCT/type: yes/0
Extra: 01cee186d9ffe5f221aa9b784d9d809278d266dee5935b195fd1de8a14aa8554af0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f6ec83e5f21c92050186bbdb47f1b2552fac41148efe98834220600db5e9e46 0.600000000000 1384850 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": 927060, "vin": [ { "gen": { "height": 927050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f6ec83e5f21c92050186bbdb47f1b2552fac41148efe98834220600db5e9e46" } } ], "extra": [ 1, 206, 225, 134, 217, 255, 229, 242, 33, 170, 155, 120, 77, 157, 128, 146, 120, 210, 102, 222, 229, 147, 91, 25, 95, 209, 222, 138, 20, 170, 133, 84, 175, 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