Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: baf721eb63b3b5f80bf8606fd6810973249e33c1dc02f7bd64daa010e90bca30

Tx prefix hash: 3be5d0186aab142c8bd5fa39c85b6c86da1a7c13955669cab55e66dd1c5901c5
Tx public key: e929793f6fc4db235b7219a55cbf02988a5dd9bc4d07fae830b37391f7fb33ea
Timestamp: 1757971006 Timestamp [UTC]: 2025-09-15 21:16:46 Age [y:d:h:m:s]: 00:343:02:03:13
Block: 1369245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251031 RingCT/type: yes/0
Extra: 01e929793f6fc4db235b7219a55cbf02988a5dd9bc4d07fae830b37391f7fb33ea021100000002ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 72ec8b3464c589ceecf64671c7176ac64bd164c67d34fbab7aad28882e0a0b8b 0.000600000000 1857320 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": 1369255, "vin": [ { "gen": { "height": 1369245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72ec8b3464c589ceecf64671c7176ac64bd164c67d34fbab7aad28882e0a0b8b" } } ], "extra": [ 1, 233, 41, 121, 63, 111, 196, 219, 35, 91, 114, 25, 165, 92, 191, 2, 152, 138, 93, 217, 188, 77, 7, 250, 232, 48, 179, 115, 145, 247, 251, 51, 234, 2, 17, 0, 0, 0, 2, 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: