Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ba7d7640d8876264459d911d8f58b0bd4745ccfb75ca54dd2ead31914e0c20f

Tx prefix hash: 4bd54cc4b066cd4af477d33d406d7ae1071fae721d670d716b1168d9ad86d6fe
Tx public key: ce7df80d069fa22688b111363b912da9410c7395a23c70de87c3206cd1fa1589
Timestamp: 1753867972 Timestamp [UTC]: 2025-07-30 09:32:52 Age [y:d:h:m:s]: 01:114:01:53:32
Block: 1336551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346829 RingCT/type: yes/0
Extra: 01ce7df80d069fa22688b111363b912da9410c7395a23c70de87c3206cd1fa1589021100000003ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 90b442bb02f840aaf921625c57f4a3329dbd4c88f236a107d9fc5a4a0d0882f9 0.000600000000 1824352 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": 1336561, "vin": [ { "gen": { "height": 1336551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90b442bb02f840aaf921625c57f4a3329dbd4c88f236a107d9fc5a4a0d0882f9" } } ], "extra": [ 1, 206, 125, 248, 13, 6, 159, 162, 38, 136, 177, 17, 54, 59, 145, 45, 169, 65, 12, 115, 149, 162, 60, 112, 222, 135, 195, 32, 108, 209, 250, 21, 137, 2, 17, 0, 0, 0, 3, 173, 121, 72, 208, 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: