Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f26691c0bbc10bfe5736a037d80e6ba7c2c44adf76935233d60617f27a4e699

Tx prefix hash: 256f4054ab64eb0ddd477fe7c6b9d98e8ebac2510960285a981d7691cad1fdfc
Tx public key: c4b3605fb9319926294c112feea10176c1460f065ea1314b653f72a325363242
Timestamp: 1758875275 Timestamp [UTC]: 2025-09-26 08:27:55 Age [y:d:h:m:s]: 01:056:06:25:25
Block: 1376741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306740 RingCT/type: yes/0
Extra: 01c4b3605fb9319926294c112feea10176c1460f065ea1314b653f72a325363242021100000002ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d0cd10cd8ab0296f67c924fe99b9d7bf6571b15e4aa3edc9e14c5129a1e0aaad 0.000600000000 1864832 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": 1376751, "vin": [ { "gen": { "height": 1376741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0cd10cd8ab0296f67c924fe99b9d7bf6571b15e4aa3edc9e14c5129a1e0aaad" } } ], "extra": [ 1, 196, 179, 96, 95, 185, 49, 153, 38, 41, 76, 17, 47, 238, 161, 1, 118, 193, 70, 15, 6, 94, 161, 49, 75, 101, 63, 114, 163, 37, 54, 50, 66, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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: