Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfda29b42e0c393ce07948472a08ae690d50649726a241d0fac5a5c744299fdb

Tx prefix hash: 4e7946b042f754d4b03b0f1060343ba0a02e7aff2545f8e502dffe25431df6ea
Tx public key: aa066617ee69e614aadbeb451f7da3639fef4a7ebd6e6b2339948632d73c7c8b
Timestamp: 1787355569 Timestamp [UTC]: 2026-08-21 23:39:29 Age [y:d:h:m:s]: 00:087:07:20:04
Block: 1618531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 61683 RingCT/type: yes/0
Extra: 01aa066617ee69e614aadbeb451f7da3639fef4a7ebd6e6b2339948632d73c7c8b0208cf2095b9e7715cef

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 96017533ed20aed17e5cb3dba3cff4deef912f90d0bb8d191cd16dffb456b06e 0.000600000000 2108551 of 15 <70>

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": 1618541, "vin": [ { "gen": { "height": 1618531 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "96017533ed20aed17e5cb3dba3cff4deef912f90d0bb8d191cd16dffb456b06e", "view_tag": "70" } } } ], "extra": [ 1, 170, 6, 102, 23, 238, 105, 230, 20, 170, 219, 235, 69, 31, 125, 163, 99, 159, 239, 74, 126, 189, 110, 107, 35, 57, 148, 134, 50, 215, 60, 124, 139, 2, 8, 207, 32, 149, 185, 231, 113, 92, 239 ], "rct_signatures": { "type": 0 } }


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