← previous blocknext block →recent activity
Analyzing
Block #95,033,178
5 transactions · 5 stateful · 2026-08-11 10:06:01 UTC
Parallelism
20/100
Blocked
60%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,033,178 · 5 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
1w02w13w24w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0xe84ca9a7…b041
0x34b655…2a6f
4 touches
1 conflict
0x05527801…9c11
0x34b655…2a6f
2 touches
0 conflicts
0x1404b00b…d8b3
0x34b655…2a6f
2 touches
0 conflicts
0x2d58a69f…6820
0x34b655…2a6f
2 touches
0 conflicts
0x300ea4a0…ee47
0x34b655…2a6f
2 touches
0 conflicts
0x3b689fd2…629c
0x34b655…2a6f
2 touches
0 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: Perpl
1 conflict on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity