Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f726042f1bff116fdbacb324861efee01530ea82587fffa18d25ff69095a9be

Tx prefix hash: ae8dac1b80336e1fcc06d9d0a618704f7b9a0202c5cb2bbaadb1f59c1bfd3524
Tx public key: 76f9ad1c4ab385f52fee069b891c5a0d23d57f1a3dd3b650ebf9d03c45f41945
Timestamp: 1761021454 Timestamp [UCT]: 2025-10-21 04:37:34 Age [y:d:h:m:s]: 00:074:07:13:36
Block: 1394540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53193 RingCT/type: yes/0
Extra: 0176f9ad1c4ab385f52fee069b891c5a0d23d57f1a3dd3b650ebf9d03c45f4194502110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a518b266379e7a868ed378d2e1f7c775cead806aa9caeab9e2b27d76f615dc2f 0.600000000000 1882811 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": 1394550, "vin": [ { "gen": { "height": 1394540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a518b266379e7a868ed378d2e1f7c775cead806aa9caeab9e2b27d76f615dc2f" } } ], "extra": [ 1, 118, 249, 173, 28, 74, 179, 133, 245, 47, 238, 6, 155, 137, 28, 90, 13, 35, 213, 127, 26, 61, 211, 182, 80, 235, 249, 208, 60, 69, 244, 25, 69, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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