Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5ffe5eaba8cc6c7d641d9d9f7d64c10d619a7791df6ee77a355be11694e47e2

Tx prefix hash: 59501f00f95af50f402ba5dad66865ac3b9734f236dc3a798a66ed316d993515
Tx public key: 8aed49d30c3c9a7bcc8b3ee46f451a8e6203748e0a367447708006f833982e8e
Timestamp: 1784391515 Timestamp [UTC]: 2026-07-18 16:18:35 Age [y:d:h:m:s]: 00:126:07:00:47
Block: 1584602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 98892 RingCT/type: yes/0
Extra: 018aed49d30c3c9a7bcc8b3ee46f451a8e6203748e0a367447708006f833982e8e02081d683745cf0f189b

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1cdfac2a0044eca1afe9c9be0bf1247614506c10a113f8a9e904a91e53c082e3 0.000600000000 2074596 of 15 <1d>

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": 1584612, "vin": [ { "gen": { "height": 1584602 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "1cdfac2a0044eca1afe9c9be0bf1247614506c10a113f8a9e904a91e53c082e3", "view_tag": "1d" } } } ], "extra": [ 1, 138, 237, 73, 211, 12, 60, 154, 123, 204, 139, 62, 228, 111, 69, 26, 142, 98, 3, 116, 142, 10, 54, 116, 71, 112, 128, 6, 248, 51, 152, 46, 142, 2, 8, 29, 104, 55, 69, 207, 15, 24, 155 ], "rct_signatures": { "type": 0 } }


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