Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04121d8a05abe0a7403d245f4385699abdc0c7c1ab0760daef903085b39e8ee9

Tx prefix hash: 4ec9d568b069a06aa8138e881aacc6397e5a11fe9aa96405cea0c779ae08403f
Tx public key: 6f9ed421d0eb642a3318a0aef52a49e682ef24926e67b2c47015fc863d4c204f
Timestamp: 1787239712 Timestamp [UTC]: 2026-08-20 15:28:32 Age [y:d:h:m:s]: 00:092:14:05:49
Block: 1617562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 65635 RingCT/type: yes/0
Extra: 016f9ed421d0eb642a3318a0aef52a49e682ef24926e67b2c47015fc863d4c204f0208d87ff8c840e1b5dd

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c2600c685502a1c0c3e8c2ef199303c38eb4fe562d97dfce6293bb51f2ea4585 0.000600000000 2107582 of 15 <64>

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": 1617572, "vin": [ { "gen": { "height": 1617562 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "c2600c685502a1c0c3e8c2ef199303c38eb4fe562d97dfce6293bb51f2ea4585", "view_tag": "64" } } } ], "extra": [ 1, 111, 158, 212, 33, 208, 235, 100, 42, 51, 24, 160, 174, 245, 42, 73, 230, 130, 239, 36, 146, 110, 103, 178, 196, 112, 21, 252, 134, 61, 76, 32, 79, 2, 8, 216, 127, 248, 200, 64, 225, 181, 221 ], "rct_signatures": { "type": 0 } }


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