Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a57768bb4170471ab4f5decdae95e158b166de07c344906412591beb4be55609

Tx prefix hash: 0684635f3d4ab3eabb84bd2d756a75cea0b11689647f5651be023b4a7ce329f6
Tx public key: 0b18c2c465e2f2d6a2d7f28ee626bef3d2f6b8829df738dc1b660ade74833d7a
Timestamp: 1771226609 Timestamp [UTC]: 2026-02-16 07:23:29 Age [y:d:h:m:s]: 00:085:13:57:24
Block: 1478896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53482 RingCT/type: yes/0
Extra: 010b18c2c465e2f2d6a2d7f28ee626bef3d2f6b8829df738dc1b660ade74833d7a021100000001e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fd1a3b01c23b0632cd46614d509979b92879294f6b474f6c538df24d66ea1cd9 0.000600000000 1968228 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": 1478906, "vin": [ { "gen": { "height": 1478896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd1a3b01c23b0632cd46614d509979b92879294f6b474f6c538df24d66ea1cd9" } } ], "extra": [ 1, 11, 24, 194, 196, 101, 226, 242, 214, 162, 215, 242, 142, 230, 38, 190, 243, 210, 246, 184, 130, 157, 247, 56, 220, 27, 102, 10, 222, 116, 131, 61, 122, 2, 17, 0, 0, 0, 1, 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: