Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42ef3d4e60e1c227af0f6b9da20e38490cc0d855eda76ea80f4e7e01cb1f00e6

Tx prefix hash: 4a4562321d6695741a2a36d1f1d6bc57037674e6701e9a8295a93b129cdf8c2a
Tx public key: acd63a37c4ac1c266f0de4075ef8a928cd3088ba78557898265607cbee037f9c
Timestamp: 1574437798 Timestamp [UTC]: 2019-11-22 15:49:58 Age [y:d:h:m:s]: 06:092:21:54:45
Block: 14562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1468114 RingCT/type: yes/0
Extra: 01acd63a37c4ac1c266f0de4075ef8a928cd3088ba78557898265607cbee037f9c0211000000060b4dd45a000000000000000000

1 output(s) for total of 0.549225804683 xmr

stealth address amount amount idx tag
00: 114f05f1a92e368065c1fb2642ef8f056aa73ec7b5ded3bc3cce555a7020aee5 0.549225804683 18599 of 0 -

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 dinastycoin-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": 14572, "vin": [ { "gen": { "height": 14562 } } ], "vout": [ { "amount": 549225804683, "target": { "key": "114f05f1a92e368065c1fb2642ef8f056aa73ec7b5ded3bc3cce555a7020aee5" } } ], "extra": [ 1, 172, 214, 58, 55, 196, 172, 28, 38, 111, 13, 228, 7, 94, 248, 169, 40, 205, 48, 136, 186, 120, 85, 120, 152, 38, 86, 7, 203, 238, 3, 127, 156, 2, 17, 0, 0, 0, 6, 11, 77, 212, 90, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369