Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07ad50c4e0b5e626178c61becf4b61ee94d1e551cbd3d32467f941b2d320ec66

Tx prefix hash: 29046a8d0944ca6a8afa86261ddf5e5509f6be2583627c86ff93c7dc50554b20
Tx public key: bceea218b8051a91ee8d038dfdda11a98b4dca5109de3f8a4e14f606c256b910
Timestamp: 1760798754 Timestamp [UCT]: 2025-10-18 14:45:54 Age [y:d:h:m:s]: 00:076:11:43:00
Block: 1392696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54758 RingCT/type: yes/0
Extra: 01bceea218b8051a91ee8d038dfdda11a98b4dca5109de3f8a4e14f606c256b9100211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd35f9b14e94602e54809a7f73d2dda5d2a9fa3adf5c380c4f433990789cd38e 0.600000000000 1880949 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": 1392706, "vin": [ { "gen": { "height": 1392696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd35f9b14e94602e54809a7f73d2dda5d2a9fa3adf5c380c4f433990789cd38e" } } ], "extra": [ 1, 188, 238, 162, 24, 184, 5, 26, 145, 238, 141, 3, 141, 253, 218, 17, 169, 139, 77, 202, 81, 9, 222, 63, 138, 78, 20, 246, 6, 194, 86, 185, 16, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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