Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb623b9a8d4afb92b02a2a3220fa022fbda84b18593602a1e65f39bb1a697070

Tx prefix hash: 44e9e9141c4fd461706b9667b4d138ee7b854cde73c04370f29ac00136f3dc77
Tx public key: 51668f6c5ec4f753f8c435b32e07112b69fbe5acb774f92ae8281d3cd1e76130
Timestamp: 1757521606 Timestamp [UCT]: 2025-09-10 16:26:46 Age [y:d:h:m:s]: 00:069:01:27:06
Block: 1365524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49450 RingCT/type: yes/0
Extra: 0151668f6c5ec4f753f8c435b32e07112b69fbe5acb774f92ae8281d3cd1e76130021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 063ed648ae7f36ac6a5864c2091eb6f1ae73ff31d7cc863b554e88fa7c53d7b8 0.600000000000 1853563 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": 1365534, "vin": [ { "gen": { "height": 1365524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "063ed648ae7f36ac6a5864c2091eb6f1ae73ff31d7cc863b554e88fa7c53d7b8" } } ], "extra": [ 1, 81, 102, 143, 108, 94, 196, 247, 83, 248, 196, 53, 179, 46, 7, 17, 43, 105, 251, 229, 172, 183, 116, 249, 42, 232, 40, 29, 60, 209, 231, 97, 48, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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