← previous blocknext block →recent activity
Analyzing
Block #75,742,026
12 transactions · 12 stateful · 2026-05-20 02:50:33 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,742,026 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w29w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xeb5b61a2…b2bc
0x34b655…2a6f
6 touches
3 conflicts
0x374426df…f445
0xc8689a…ee79
4 touches
1 conflict
0x10814d14…cdda
0x34b655…2a6f
4 touches
1 conflict
0x46449565…6464
0x34b655…2a6f
4 touches
1 conflict
0x689cd5fd…5556
0x34b655…2a6f
4 touches
1 conflict
0x756c9558…80c6
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
3 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity