Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eed232e5f57248d86a8a741d868e7509c335c8681c10c12b4838d4613bff2c2b

Tx prefix hash: c2997ca7cced3f22128d843e1ed3dab3d8c7445a9eb1ccf714f72cd4bb03b931
Tx public key: e091cd9e1b68e9bef10ec7defbf9466e4ce818e1dadfd08bdf72ded96b90f116
Timestamp: 1762936573 Timestamp [UCT]: 2025-11-12 08:36:13 Age [y:d:h:m:s]: 00:081:01:04:24
Block: 1410391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57848 RingCT/type: yes/0
Extra: 01e091cd9e1b68e9bef10ec7defbf9466e4ce818e1dadfd08bdf72ded96b90f116021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a60713010fc0024d7910740948b3d919eca773cac896e6dfe3af3b5885b9e23a 0.600000000000 1898842 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": 1410401, "vin": [ { "gen": { "height": 1410391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a60713010fc0024d7910740948b3d919eca773cac896e6dfe3af3b5885b9e23a" } } ], "extra": [ 1, 224, 145, 205, 158, 27, 104, 233, 190, 241, 14, 199, 222, 251, 249, 70, 110, 76, 232, 24, 225, 218, 223, 208, 139, 223, 114, 222, 217, 107, 144, 241, 22, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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