Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fec2c4ef7f874ae275db0bd1d87612d8ef1eef969971e3810b419dee3d71410f

Tx prefix hash: 17c86896ffdc05130c8845b4c65667a5d5adc58771e92b537e8746d0fa44ce41
Tx public key: b8e59f14c698bd976685897b51a807b46bb2852f4c5b5c977beae6aa36e43af1
Timestamp: 1744440075 Timestamp [UTC]: 2025-04-12 06:41:15 Age [y:d:h:m:s]: 01:216:18:06:07
Block: 1259678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418838 RingCT/type: yes/0
Extra: 01b8e59f14c698bd976685897b51a807b46bb2852f4c5b5c977beae6aa36e43af10211000000066c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 159d1b0e47a2494d7dbd73bca2c0ea398c11c60a5f868b33e25659ddcbb39f17 0.000600000000 1746827 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": 1259688, "vin": [ { "gen": { "height": 1259678 } } ], "vout": [ { "amount": 600000000, "target": { "key": "159d1b0e47a2494d7dbd73bca2c0ea398c11c60a5f868b33e25659ddcbb39f17" } } ], "extra": [ 1, 184, 229, 159, 20, 198, 152, 189, 151, 102, 133, 137, 123, 81, 168, 7, 180, 107, 178, 133, 47, 76, 91, 92, 151, 123, 234, 230, 170, 54, 228, 58, 241, 2, 17, 0, 0, 0, 6, 108, 152, 170, 61, 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: