Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f682d2cc2d543d0d58915060b345732cfcb926d81f46efac7fe7204c066ab90

Tx prefix hash: fcfd61ec3a8fdf1f3375915c693cb897b21518c8728d44ee1c914b869191670c
Tx public key: 6e03424eb047adcd8cd4a695b68a37a2472ef48e09e52a3533ec5d2b43e3fd97
Timestamp: 1750544543 Timestamp [UCT]: 2025-06-21 22:22:23 Age [y:d:h:m:s]: 00:151:23:37:54
Block: 1310053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106465 RingCT/type: yes/0
Extra: 016e03424eb047adcd8cd4a695b68a37a2472ef48e09e52a3533ec5d2b43e3fd970211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 300d8805f24274910b748b0ca34f0bff64bfb90f284e59739420496bcf26370e 0.600000000000 1797670 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": 1310063, "vin": [ { "gen": { "height": 1310053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "300d8805f24274910b748b0ca34f0bff64bfb90f284e59739420496bcf26370e" } } ], "extra": [ 1, 110, 3, 66, 78, 176, 71, 173, 205, 140, 212, 166, 149, 182, 138, 55, 162, 71, 46, 244, 142, 9, 229, 42, 53, 51, 236, 93, 43, 67, 227, 253, 151, 2, 17, 0, 0, 0, 1, 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