Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97fb42e66739b64c94386f5c7b851690dea791bb36059d3f12c4ba1165c6e567

Tx prefix hash: 26161472f167e5a9096f93519d9310c458c9b276bb30412e35e9e85f24ac3c58
Tx public key: 47d0eff085c93f0a2932087eab640f69badc7e0ec89e97d1fcf968f123cc6b7d
Timestamp: 1726302299 Timestamp [UCT]: 2024-09-14 08:24:59 Age [y:d:h:m:s]: 00:206:16:32:38
Block: 1109797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147556 RingCT/type: yes/0
Extra: 0147d0eff085c93f0a2932087eab640f69badc7e0ec89e97d1fcf968f123cc6b7d021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26eb845a9626d4937d3b56e291b7f0ff9280969e28b4ad9ec3343dff5797a91a 0.600000000000 1588180 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": 1109807, "vin": [ { "gen": { "height": 1109797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26eb845a9626d4937d3b56e291b7f0ff9280969e28b4ad9ec3343dff5797a91a" } } ], "extra": [ 1, 71, 208, 239, 240, 133, 201, 63, 10, 41, 50, 8, 126, 171, 100, 15, 105, 186, 220, 126, 14, 200, 158, 151, 209, 252, 249, 104, 241, 35, 204, 107, 125, 2, 17, 0, 0, 0, 4, 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