Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d0eeeb77fa30f23dc7516918eb4cced57fb0eae59ecf52d0444fc4b4d0b9a8c

Tx prefix hash: 1041357ee4cb90c27bfdff4c1964a24a1f2aaef1c706b97ca1204f72ad2931ac
Tx public key: 6664bc8572cad34315328dd50c77f0e15022687c5771d67bf468b06c287d33c0
Timestamp: 1771244067 Timestamp [UTC]: 2026-02-16 12:14:27 Age [y:d:h:m:s]: 00:092:20:57:04
Block: 1479046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59833 RingCT/type: yes/0
Extra: 016664bc8572cad34315328dd50c77f0e15022687c5771d67bf468b06c287d33c0021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 34c89e979c963e91e852a8f696e3688e881ed90a250277a479a66dbce7d0da91 0.000600000000 1968380 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": 1479056, "vin": [ { "gen": { "height": 1479046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34c89e979c963e91e852a8f696e3688e881ed90a250277a479a66dbce7d0da91" } } ], "extra": [ 1, 102, 100, 188, 133, 114, 202, 211, 67, 21, 50, 141, 213, 12, 119, 240, 225, 80, 34, 104, 124, 87, 113, 214, 123, 244, 104, 176, 108, 40, 125, 51, 192, 2, 17, 0, 0, 0, 5, 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: