Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a111a4ed03f361efb0b0c5d3279246cb48d065f3aa7daa7e2bca43c71844c0db

Tx prefix hash: defc8d57116053d4a707fb19969b52d88b55b9b8429abcf12803d88b082b947f
Tx public key: 7dac5350b85a0768744609520e81fe325df41ff1dad4c3a88438e8bd07340c18
Timestamp: 1770232336 Timestamp [UTC]: 2026-02-04 19:12:16 Age [y:d:h:m:s]: 00:282:07:30:42
Block: 1470695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207130 RingCT/type: yes/0
Extra: 017dac5350b85a0768744609520e81fe325df41ff1dad4c3a88438e8bd07340c18021100000009f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 75fc41e7857866387094efe6127e8da05fa47b6f6d60398d7d26e25ccfc514ee 0.000600000000 1959963 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": 1470705, "vin": [ { "gen": { "height": 1470695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75fc41e7857866387094efe6127e8da05fa47b6f6d60398d7d26e25ccfc514ee" } } ], "extra": [ 1, 125, 172, 83, 80, 184, 90, 7, 104, 116, 70, 9, 82, 14, 129, 254, 50, 93, 244, 31, 241, 218, 212, 195, 168, 132, 56, 232, 189, 7, 52, 12, 24, 2, 17, 0, 0, 0, 9, 241, 136, 200, 168, 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: