← previous blocknext block →recent activity
Analyzing
Block #94,668,612
20 transactions · 19 stateful · 2026-08-10 03:30:39 UTC
Parallelism
80/100
Blocked
26%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,668,612 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w111w012w113w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x21de4cce…a3e9
0x34b655…2a6f
6 touches
3 conflicts
0xf4f9cac7…fd98
0x34b655…2a6f
6 touches
3 conflicts
0x977f2411…89f7
0x34b655…2a6f
6 touches
3 conflicts
0xc9ba1c61…1c8e
0x34b655…2a6f
6 touches
3 conflicts
0xeea6de0f…51bc
0x34b655…2a6f
5 touches
3 conflicts
0x8247a6fd…00b6
0x34b655…2a6f
4 touches
1 conflict
0x8b8a50e1…b5dc
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity