Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e9c45152ba6a2438449769df0e879194ebd825501b180d3d578d487ab538368

Tx prefix hash: cf2dd4a04c4457792dfdc45426995e56c1bcc020b8bc8de24a277e740cc9704c
Tx public key: 5f3de532976e7e3466fc68bfa3fbb2916ac5c4e3858d71bed968b416f2bda357
Timestamp: 1723100548 Timestamp [UCT]: 2024-08-08 07:02:28 Age [y:d:h:m:s]: 00:245:17:16:26
Block: 1083255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175511 RingCT/type: yes/0
Extra: 015f3de532976e7e3466fc68bfa3fbb2916ac5c4e3858d71bed968b416f2bda357021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63300be8d3aa1c0ca11e4bcac1666cf408073cf40b784aa7b0e11abc4d1b2d12 0.600000000000 1557104 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": 1083265, "vin": [ { "gen": { "height": 1083255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63300be8d3aa1c0ca11e4bcac1666cf408073cf40b784aa7b0e11abc4d1b2d12" } } ], "extra": [ 1, 95, 61, 229, 50, 151, 110, 126, 52, 102, 252, 104, 191, 163, 251, 178, 145, 106, 197, 196, 227, 133, 141, 113, 190, 217, 104, 180, 22, 242, 189, 163, 87, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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