Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba99ec6aa16c2135fe3fcacfebdb9a11261dccd964df80e58cb776caddf6290d

Tx prefix hash: 0c1837620be7ee6b93ab5563b0a8d7f54ff50642d8a4fbd4a6530573728f247d
Tx public key: 4bd69788ab2c48b4221a8a46e553c1cb0262a28fa1596527853aa21b44ed99df
Timestamp: 1765712429 Timestamp [UTC]: 2025-12-14 11:40:29 Age [y:d:h:m:s]: 00:339:05:01:28
Block: 1433395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247856 RingCT/type: yes/0
Extra: 014bd69788ab2c48b4221a8a46e553c1cb0262a28fa1596527853aa21b44ed99df02110000000170609d03000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 613b6b24410e1d85a9ebe05320d9dd04d261bea7a794d81ce7fd574d2f1e67ad 0.000600000000 1922174 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": 1433405, "vin": [ { "gen": { "height": 1433395 } } ], "vout": [ { "amount": 600000000, "target": { "key": "613b6b24410e1d85a9ebe05320d9dd04d261bea7a794d81ce7fd574d2f1e67ad" } } ], "extra": [ 1, 75, 214, 151, 136, 171, 44, 72, 180, 34, 26, 138, 70, 229, 83, 193, 203, 2, 98, 162, 143, 161, 89, 101, 39, 133, 58, 162, 27, 68, 237, 153, 223, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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: