← previous blocknext block →recent activity
Analyzing
Block #75,478,335
20 transactions · 18 stateful · 2026-05-18 21:23:50 UTC
Parallelism
60/100
Blocked
56%
Avg conflicts / tx
1.6
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #75,478,335 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w17w38w29w414w415w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6cc7de8…0b4a
0x3bd359…433a
12 touches
15 conflicts
0x00000000…0004
0x63e48b…53f2
12 touches
15 conflicts
0x00000000…0000
0x63e48b…53f2
12 touches
15 conflicts
0x9a555477…19a8
0x754704…b603
12 touches
15 conflicts
0x00000000…0002
0x63e48b…53f2
10 touches
10 conflicts
0x17606ba6…1b6e
0x754704…b603
10 touches
10 conflicts
0x00000000…0005
0x63e48b…53f2
8 touches
6 conflicts
0x3e20a53a…3b5e
0x63e48b…53f2
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Wrapped MON (WMON)
15 conflicts on slot 0xf6cc7de8cb…7d0b4a
Audit this contract →
← previous block·next block →recent activity