Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b71c0ecc8708a50411cac9cf3bdb73146080df451ea8bd0368e3cf8b701e235

Tx prefix hash: bfec72783c8275e3a0247e8fdfad619aff88b9d248f308fc9d2f6b5b9cd2732a
Tx public key: 0e29579c0dda52e5e5c6043b1622f2eceef53dbab82e87df4fc74c507ccd3ffd
Timestamp: 1743244400 Timestamp [UTC]: 2025-03-29 10:33:20 Age [y:d:h:m:s]: 01:050:16:14:55
Block: 1249776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287753 RingCT/type: yes/0
Extra: 010e29579c0dda52e5e5c6043b1622f2eceef53dbab82e87df4fc74c507ccd3ffd0211000000019ba629df000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3c4f2a72dd33ed027785a63384ad1a30db822767b0c423acf9d9ef7c06dfd1cc 0.000600000000 1736817 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": 1249786, "vin": [ { "gen": { "height": 1249776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c4f2a72dd33ed027785a63384ad1a30db822767b0c423acf9d9ef7c06dfd1cc" } } ], "extra": [ 1, 14, 41, 87, 156, 13, 218, 82, 229, 229, 198, 4, 59, 22, 34, 242, 236, 238, 245, 61, 186, 184, 46, 135, 223, 79, 199, 76, 80, 124, 205, 63, 253, 2, 17, 0, 0, 0, 1, 155, 166, 41, 223, 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: