← previous blocknext block →recent activity
Analyzing
Block #95,268,268
14 transactions · 12 stateful · 2026-08-12 05:57:57 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,268,268 · 14 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
1w06w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x66d5e476…8a1f
0x34b655…2a6f
4 touches
1 conflict
0xefd234e9…5b03
0x34b655…2a6f
4 touches
1 conflict
0x6920b1b8…c725
0x34b655…2a6f
3 touches
1 conflict
0x1526b11f…8b21
0x34b655…2a6f
2 touches
0 conflicts
0x1795ff28…210c
0x34b655…2a6f
2 touches
0 conflicts
0x1cd6787c…8a13
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 0x261cbea79d…12e35e
Audit this contract →
← previous block·next block →recent activity