Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2ee06f3085580ab6ec9de4a728c17f317bdb1c9ff3c444689cd2baf82e637f6

Tx prefix hash: 478998e5ce4b8ea15b48c2454f686af1939cc573ecb96317ceb9b6a07da0834d
Tx public key: ad927407f8cc3fcc1fbd5369f73356118c6da6a09553be97a47017daab9a19c4
Timestamp: 1743989105 Timestamp [UTC]: 2025-04-07 01:25:05 Age [y:d:h:m:s]: 01:227:10:54:17
Block: 1255926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426750 RingCT/type: yes/0
Extra: 01ad927407f8cc3fcc1fbd5369f73356118c6da6a09553be97a47017daab9a19c40211000000016c98aa3d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 270c4c8e39e866b0414510d59aa1592522725c4b2d00d0cf8e93f7e415cd808a 0.000600000000 1743033 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": 1255936, "vin": [ { "gen": { "height": 1255926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "270c4c8e39e866b0414510d59aa1592522725c4b2d00d0cf8e93f7e415cd808a" } } ], "extra": [ 1, 173, 146, 116, 7, 248, 204, 63, 204, 31, 189, 83, 105, 247, 51, 86, 17, 140, 109, 166, 160, 149, 83, 190, 151, 164, 112, 23, 218, 171, 154, 25, 196, 2, 17, 0, 0, 0, 1, 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: