← previous blocknext block →recent activity
Analyzing
Block #95,276,520
16 transactions · 15 stateful · 2026-08-12 06:39:35 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,276,520 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w112w014w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9aea124d…de52
0x34b655…2a6f
4 touches
1 conflict
0x0ae2991a…6a02
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0df3b1db…727b
0x34b655…2a6f
4 touches
1 conflict
0x6518075e…2b17
0x2a68ba…90c5
4 touches
1 conflict
0x68720e4e…b4e6
0x40c49f…2af0
3 touches
1 conflict
0x3f25409b…f92b
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4aa
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 0x9aea124d13…7ade52
Audit this contract →
← previous block·next block →recent activity