Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd0389c02b229b475aa54319b11977253d2661283d330a06b7a1f8a307f70483

Tx prefix hash: cc5078f5e31761de5a04159068994ac2481564ddd6689bf03620d48da72ac55c
Tx public key: 718f8bec37eeb1a668c0bd264e93ad1ad3b27fd3ac047082269b4abc4896cf10
Timestamp: 1732311208 Timestamp [UCT]: 2024-11-22 21:33:28 Age [y:d:h:m:s]: 00:360:16:37:01
Block: 1159521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255337 RingCT/type: yes/0
Extra: 01718f8bec37eeb1a668c0bd264e93ad1ad3b27fd3ac047082269b4abc4896cf100211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 570e41bbe86fc69fd8a2c05d4a0b61f723a20be6ef8c7abc5c0a7a10d9da773f 0.600000000000 1645158 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": 1159531, "vin": [ { "gen": { "height": 1159521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "570e41bbe86fc69fd8a2c05d4a0b61f723a20be6ef8c7abc5c0a7a10d9da773f" } } ], "extra": [ 1, 113, 143, 139, 236, 55, 238, 177, 166, 104, 192, 189, 38, 78, 147, 173, 26, 211, 178, 127, 211, 172, 4, 112, 130, 38, 155, 74, 188, 72, 150, 207, 16, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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