Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41cd8c01a9fee83eb5891d321d056da65cdc71df4bbb4b18a7a710cddd4c0b8e

Tx prefix hash: 054a7092496e6d10d5b82cd078c1480f23113c7471fca6b95e44e61ffcc756eb
Tx public key: 534882010c7f6540a57dffb1c15860ab79cf8f5d53860463a30839cc076805be
Timestamp: 1760651086 Timestamp [UTC]: 2025-10-16 21:44:46 Age [y:d:h:m:s]: 01:034:03:03:36
Block: 1391457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290820 RingCT/type: yes/0
Extra: 01534882010c7f6540a57dffb1c15860ab79cf8f5d53860463a30839cc076805be0211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 655ccc81406b0a197cc8563cd8bbc5e14a55e0e6a02d7e6bf5cc948a38b6082d 0.000600000000 1879704 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": 1391467, "vin": [ { "gen": { "height": 1391457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "655ccc81406b0a197cc8563cd8bbc5e14a55e0e6a02d7e6bf5cc948a38b6082d" } } ], "extra": [ 1, 83, 72, 130, 1, 12, 127, 101, 64, 165, 125, 255, 177, 193, 88, 96, 171, 121, 207, 143, 93, 83, 134, 4, 99, 163, 8, 57, 204, 7, 104, 5, 190, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: