Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adaeb54d356d9b67e01f067cddb38915830aae98bb03de93e0216584d67d4bfe

Tx prefix hash: 5909b4e09396cda93c334916aaf5ae4ae914a88a07c4e7b5f5739d47812397f0
Tx public key: d7d19bf6204d65d0b9030d0277b7c68551771db41747e4edd08435b9f729ea02
Timestamp: 1726426978 Timestamp [UCT]: 2024-09-15 19:02:58 Age [y:d:h:m:s]: 00:069:18:47:26
Block: 1110837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 49893 RingCT/type: yes/0
Extra: 01d7d19bf6204d65d0b9030d0277b7c68551771db41747e4edd08435b9f729ea02021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef541ecf6e901719e337dd31351c37c1f26af44e3c261305b6c918c0e02fc2f9 0.600000000000 1589586 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": 1110847, "vin": [ { "gen": { "height": 1110837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef541ecf6e901719e337dd31351c37c1f26af44e3c261305b6c918c0e02fc2f9" } } ], "extra": [ 1, 215, 209, 155, 246, 32, 77, 101, 208, 185, 3, 13, 2, 119, 183, 198, 133, 81, 119, 29, 180, 23, 71, 228, 237, 208, 132, 53, 185, 247, 41, 234, 2, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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