← previous blocknext block →recent activity
Analyzing
Block #95,626,987
19 transactions · 17 stateful · 2026-08-13 12:07:03 UTC
Parallelism
74/100
Blocked
29%
Avg conflicts / tx
0.42
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,626,987 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w212w313w417w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa53c3cca…db68
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xcf17589f…048c
0x34b655…2a6f
6 touches
3 conflicts
0x88fec46a…81d0
0x34b655…2a6f
6 touches
3 conflicts
0x424934c8…f2f1
0x34b655…2a6f
4 touches
1 conflict
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x5a19ef35…dc70
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0xa53c3cca68…a5db68
Audit this contract →
← previous block·next block →recent activity