Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c40047d3376b8469f73d1db411bbaa85734160fe5b89e33daad7dcf7c556e47

Tx prefix hash: 33843ad06af8f552444c5c6c671085638d91523a9cfb36dda51490ad2e0c6a4e
Tx public key: 57544c73664eaa83ae2a61c78bd2fee53850d01fba598268e019473b296ecf18
Timestamp: 1756015165 Timestamp [UTC]: 2025-08-24 05:59:25 Age [y:d:h:m:s]: 01:089:20:56:17
Block: 1353218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330276 RingCT/type: yes/0
Extra: 0157544c73664eaa83ae2a61c78bd2fee53850d01fba598268e019473b296ecf180211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4305164d0e82d5a97605f5696a9c1d1705233fb2fb61628e0b5aa2c407d1b39d 0.000600000000 1841193 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": 1353228, "vin": [ { "gen": { "height": 1353218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4305164d0e82d5a97605f5696a9c1d1705233fb2fb61628e0b5aa2c407d1b39d" } } ], "extra": [ 1, 87, 84, 76, 115, 102, 78, 170, 131, 174, 42, 97, 199, 139, 210, 254, 229, 56, 80, 208, 31, 186, 89, 130, 104, 224, 25, 71, 59, 41, 110, 207, 24, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: