Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15aaffbf6e8dbc83083ac9e007684188f84950643e6c357ec3419cd39fbe93ca

Tx prefix hash: 67e22d10caf20526041f1981806171e7d3eaf90925561ffd73f10aa73f11c5e2
Tx public key: 1a171809fb1e60c169a5315dddb7344913bd3d675315e15f2761a59fdb130ae5
Timestamp: 1782889407 Timestamp [UTC]: 2026-07-01 07:03:27 Age [y:d:h:m:s]: 00:144:13:54:59
Block: 1572089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 112061 RingCT/type: yes/0
Extra: 011a171809fb1e60c169a5315dddb7344913bd3d675315e15f2761a59fdb130ae5020893bf3195b75f9eaf

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4b239d63f04648d0089ccaef266f1b2f20c9b7aff7c904006726097dfe5fd1a0 0.000600000000 2062069 of 15 <82>

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": 1572099, "vin": [ { "gen": { "height": 1572089 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "4b239d63f04648d0089ccaef266f1b2f20c9b7aff7c904006726097dfe5fd1a0", "view_tag": "82" } } } ], "extra": [ 1, 26, 23, 24, 9, 251, 30, 96, 193, 105, 165, 49, 93, 221, 183, 52, 73, 19, 189, 61, 103, 83, 21, 225, 95, 39, 97, 165, 159, 219, 19, 10, 229, 2, 8, 147, 191, 49, 149, 183, 95, 158, 175 ], "rct_signatures": { "type": 0 } }


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