Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 738ac61aec6b2b8e0eea013f0e5073a46d4e965c3ae5c03eb1884e39a233454f

Tx prefix hash: 72006e99ad35c3851c17e71e6bb2471cd14b9ea36797330a4745c72a004424bd
Tx public key: 371b73777e83fed58e1cdc5ffd5db6b2839042b460cd5d5d3bfdffd029c46fb3
Timestamp: 1578636396 Timestamp [UTC]: 2020-01-10 06:06:36 Age [y:d:h:m:s]: 06:315:17:47:21
Block: 42254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1639991 RingCT/type: yes/0
Extra: 01371b73777e83fed58e1cdc5ffd5db6b2839042b460cd5d5d3bfdffd029c46fb30211000000084943cd9f000000000000000000

1 output(s) for total of 0.444636629430 xmr

stealth address amount amount idx tag
00: 6d324838040d006fa707fa6b3be7381d7fc8de9608fcebae1cc48f18e0431221 0.444636629430 76037 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": 42264, "vin": [ { "gen": { "height": 42254 } } ], "vout": [ { "amount": 444636629430, "target": { "key": "6d324838040d006fa707fa6b3be7381d7fc8de9608fcebae1cc48f18e0431221" } } ], "extra": [ 1, 55, 27, 115, 119, 126, 131, 254, 213, 142, 28, 220, 95, 253, 93, 182, 178, 131, 144, 66, 180, 96, 205, 93, 93, 59, 253, 255, 208, 41, 196, 111, 179, 2, 17, 0, 0, 0, 8, 73, 67, 205, 159, 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) | monero version: