Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4fec2bfd4b6981ef82b8e13afb8341776f660afd4dec9aa61a4c616f5d608d3

Tx prefix hash: 6132f2ea720f0980f411a34b68bc15a16e78ab1b49dff816ebfa9c4f9afe0fe5
Tx public key: 269d32d7b5ae3160a2710ae6524b3000bd7d22592b7d3171fedce8802c4c8bde
Timestamp: 1759559324 Timestamp [UTC]: 2025-10-04 06:28:44 Age [y:d:h:m:s]: 01:042:05:46:35
Block: 1382399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296484 RingCT/type: yes/0
Extra: 01269d32d7b5ae3160a2710ae6524b3000bd7d22592b7d3171fedce8802c4c8bde02110000000197baf922000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0a71b455a02f8e25aec6ee286af8b5e170fb2de88448276badb94a75345e506b 0.000600000000 1870534 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": 1382409, "vin": [ { "gen": { "height": 1382399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a71b455a02f8e25aec6ee286af8b5e170fb2de88448276badb94a75345e506b" } } ], "extra": [ 1, 38, 157, 50, 215, 181, 174, 49, 96, 162, 113, 10, 230, 82, 75, 48, 0, 189, 125, 34, 89, 43, 125, 49, 113, 254, 220, 232, 128, 44, 76, 139, 222, 2, 17, 0, 0, 0, 1, 151, 186, 249, 34, 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: