Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6a7fd135f34ea2d02596d0c4135c00554fafa9c67b0acc48d6d78d9c9cfb5a2

Tx prefix hash: d057283436b981120cf08c1b616ced259d6cb985a34cb7ae1592a1c8192b1ffd
Tx public key: 1039219b51088329c94526d93d14b0350d99b30e7162ddd49bdcdb9aac961d44
Timestamp: 1773735057 Timestamp [UTC]: 2026-03-17 08:10:57 Age [y:d:h:m:s]: 00:245:12:35:46
Block: 1499690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180941 RingCT/type: yes/0
Extra: 011039219b51088329c94526d93d14b0350d99b30e7162ddd49bdcdb9aac961d440211000000b4e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 66468dfee5a8189b41a3b13e41a8f5d2fd9b815239e7e3516a72c9e1b74522de 0.000600000000 1989354 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": 1499700, "vin": [ { "gen": { "height": 1499690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66468dfee5a8189b41a3b13e41a8f5d2fd9b815239e7e3516a72c9e1b74522de" } } ], "extra": [ 1, 16, 57, 33, 155, 81, 8, 131, 41, 201, 69, 38, 217, 61, 20, 176, 53, 13, 153, 179, 14, 113, 98, 221, 212, 155, 220, 219, 154, 172, 150, 29, 68, 2, 17, 0, 0, 0, 180, 228, 245, 25, 63, 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: