Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a5d9ccaa98f9eb111463342f8e76838d4a7b84fe74953b634702b8cb4745278

Tx prefix hash: 123b11a8be6e086efe529d66e56f55687c9603330f6f903073d116343eb92dba
Tx public key: 2a463df0feb4b8d6f81ed70c86fa5462d340f8cf23904d92ad4525b7109f1df9
Timestamp: 1763614370 Timestamp [UCT]: 2025-11-20 04:52:50 Age [y:d:h:m:s]: 00:007:13:07:38
Block: 1416014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5409 RingCT/type: yes/0
Extra: 012a463df0feb4b8d6f81ed70c86fa5462d340f8cf23904d92ad4525b7109f1df902110000000117b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93f1f1a1a7a61f1d7a5aa9f01fe9e2a91179cfb4b76526219e47774624d810c5 0.600000000000 1904533 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": 1416024, "vin": [ { "gen": { "height": 1416014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93f1f1a1a7a61f1d7a5aa9f01fe9e2a91179cfb4b76526219e47774624d810c5" } } ], "extra": [ 1, 42, 70, 61, 240, 254, 180, 184, 214, 248, 30, 215, 12, 134, 250, 84, 98, 211, 64, 248, 207, 35, 144, 77, 146, 173, 69, 37, 183, 16, 159, 29, 249, 2, 17, 0, 0, 0, 1, 23, 177, 145, 50, 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