Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5aec14fb2bf4ff19085b4e4dc38a9713ce4b98fca6f3bc7771a860ce17c4690

Tx prefix hash: 0dc5d49d8da57b74f0c2a3019a50a65776f38110e9333511a88fde2afd61cc19
Tx public key: 2ebb14abb6e85b4ca30df6e9197e9105337e1d8dff9d040b137650e901c444f2
Timestamp: 1735887528 Timestamp [UCT]: 2025-01-03 06:58:48 Age [y:d:h:m:s]: 00:081:04:07:48
Block: 1189161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57772 RingCT/type: yes/0
Extra: 012ebb14abb6e85b4ca30df6e9197e9105337e1d8dff9d040b137650e901c444f2021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 990ef30a119d18e7fcab63a4b67daa506a469d8aa24e21a8b205e1265f0b752f 0.600000000000 1675666 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": 1189171, "vin": [ { "gen": { "height": 1189161 } } ], "vout": [ { "amount": 600000000, "target": { "key": "990ef30a119d18e7fcab63a4b67daa506a469d8aa24e21a8b205e1265f0b752f" } } ], "extra": [ 1, 46, 187, 20, 171, 182, 232, 91, 76, 163, 13, 246, 233, 25, 126, 145, 5, 51, 126, 29, 141, 255, 157, 4, 11, 19, 118, 80, 233, 1, 196, 68, 242, 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