Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aed53cc9a99537bbe27e3961677e675002a8ca007cb4eb07acb60482db7e20a7

Tx prefix hash: cac87da621ca7868f516f5f6fa5b06d74273f1b7b6ff42dfb19e9d496efddcae
Tx public key: f1c07751c0abd446c059e224553dc1aa11cc15cc222c579fc3c53753bf31d8ad
Timestamp: 1707954125 Timestamp [UCT]: 2024-02-14 23:42:05 Age [y:d:h:m:s]: 01:011:08:06:42
Block: 957680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269108 RingCT/type: yes/0
Extra: 01f1c07751c0abd446c059e224553dc1aa11cc15cc222c579fc3c53753bf31d8ad0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 467bf69492d7d896ffe1d9a1807dd6f7c0d97e0dc6ad25eea52a5969574b98f4 0.600000000000 1417006 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": 957690, "vin": [ { "gen": { "height": 957680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "467bf69492d7d896ffe1d9a1807dd6f7c0d97e0dc6ad25eea52a5969574b98f4" } } ], "extra": [ 1, 241, 192, 119, 81, 192, 171, 212, 70, 192, 89, 226, 36, 85, 61, 193, 170, 17, 204, 21, 204, 34, 44, 87, 159, 195, 197, 55, 83, 191, 49, 216, 173, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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