Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a356ff78cc492a2ea68a747a0ac30b56810bc09a716cd6a3d6fcf217aeb7e26e

Tx prefix hash: 75f9969160d7451d095eec7c750fb6755083be1365e29fdb2ce4dd00634ef9c6
Tx public key: 322d217e684336787e460566d3df0901311a4a8888f01526eabcd8415f7800a3
Timestamp: 1705364223 Timestamp [UCT]: 2024-01-16 00:17:03 Age [y:d:h:m:s]: 01:151:22:13:28
Block: 936199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369632 RingCT/type: yes/0
Extra: 01322d217e684336787e460566d3df0901311a4a8888f01526eabcd8415f7800a302110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35a55dac6459ece8e1f8915fafbb0b6b634e5e56efd219d5b76e0b4fa68fdc37 0.600000000000 1394223 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": 936209, "vin": [ { "gen": { "height": 936199 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35a55dac6459ece8e1f8915fafbb0b6b634e5e56efd219d5b76e0b4fa68fdc37" } } ], "extra": [ 1, 50, 45, 33, 126, 104, 67, 54, 120, 126, 70, 5, 102, 211, 223, 9, 1, 49, 26, 74, 136, 136, 240, 21, 38, 234, 188, 216, 65, 95, 120, 0, 163, 2, 17, 0, 0, 0, 13, 89, 218, 211, 245, 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