Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 528134429aa14dfde50720bbe49fedf2528ae0b29930a83a3b5fd618c2d880e7

Tx prefix hash: 39676720da349ec78d93ea45496388045a44d4e38fa7cccb14e862833f732444
Tx public key: b5d3fd739e83a2f177355c04a59c28a20225fae317ac10002e6ec02c3fa32677
Timestamp: 1770931745 Timestamp [UTC]: 2026-02-12 21:29:05 Age [y:d:h:m:s]: 00:281:21:49:00
Block: 1476484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207010 RingCT/type: yes/0
Extra: 01b5d3fd739e83a2f177355c04a59c28a20225fae317ac10002e6ec02c3fa3267702110000000ce4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 99c3a73fff49fb5bf1fb041357d813c171d5d22093d4228e421e5b549f2e334a 0.000600000000 1965792 of 15 -

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": 1476494, "vin": [ { "gen": { "height": 1476484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99c3a73fff49fb5bf1fb041357d813c171d5d22093d4228e421e5b549f2e334a" } } ], "extra": [ 1, 181, 211, 253, 115, 158, 131, 162, 241, 119, 53, 92, 4, 165, 156, 40, 162, 2, 37, 250, 227, 23, 172, 16, 0, 46, 110, 192, 44, 63, 163, 38, 119, 2, 17, 0, 0, 0, 12, 228, 245, 25, 63, 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: