Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8de377e18f7395c6dfb040f466a304a9f0d57ac23d2f3a75857d3a53a05b142

Tx prefix hash: f2f7382d14468b11e769bcc251d7a32be8f7d6ea3f47f874b0b4caaa4007066a
Tx public key: a56343e813f97d03ed4ef52673d447b7d19fe2a1d0ac207e04ce47b2e468996e
Timestamp: 1752913900 Timestamp [UCT]: 2025-07-19 08:31:40 Age [y:d:h:m:s]: 00:173:11:10:05
Block: 1328705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122845 RingCT/type: yes/0
Extra: 01a56343e813f97d03ed4ef52673d447b7d19fe2a1d0ac207e04ce47b2e468996e021100000004a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d796053f4e7b3bf65b61f29588e6ca6c6337b88c58080c1660c61603654fcc5 0.600000000000 1816468 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": 1328715, "vin": [ { "gen": { "height": 1328705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d796053f4e7b3bf65b61f29588e6ca6c6337b88c58080c1660c61603654fcc5" } } ], "extra": [ 1, 165, 99, 67, 232, 19, 249, 125, 3, 237, 78, 245, 38, 115, 212, 71, 183, 209, 159, 226, 161, 208, 172, 32, 126, 4, 206, 71, 178, 228, 104, 153, 110, 2, 17, 0, 0, 0, 4, 161, 29, 186, 152, 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