Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 595b10d1204f9f5306d2fc92e7b29fea223b4b5cbe1a7529e1644af2dfef66a2

Tx prefix hash: dbcc56030771304534ce852dfe0b15008afb4be43c0d24c3dface6109d84bb41
Tx public key: f52ff49b71715c8f8335ed21c94f42b883995d2e16a974178499c1831ea323e6
Timestamp: 1728899512 Timestamp [UCT]: 2024-10-14 09:51:52 Age [y:d:h:m:s]: 00:164:22:03:47
Block: 1131341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117634 RingCT/type: yes/0
Extra: 01f52ff49b71715c8f8335ed21c94f42b883995d2e16a974178499c1831ea323e6021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a796150e8976f96fdaca95930e848eafa4c1cf9a4a50b287daf4d8d49f151fbf 0.600000000000 1614236 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": 1131351, "vin": [ { "gen": { "height": 1131341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a796150e8976f96fdaca95930e848eafa4c1cf9a4a50b287daf4d8d49f151fbf" } } ], "extra": [ 1, 245, 47, 244, 155, 113, 113, 92, 143, 131, 53, 237, 33, 201, 79, 66, 184, 131, 153, 93, 46, 22, 169, 116, 23, 132, 153, 193, 131, 30, 163, 35, 230, 2, 17, 0, 0, 0, 3, 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