← previous blocknext block →recent activity
Analyzing
Block #95,246,384
12 transactions · 12 stateful · 2026-08-12 04:03:33 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,246,384 · 12 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8f203394…f2db
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x49611dcc…9864
0x34b655…2a6f
4 touches
1 conflict
0xa74ffa3b…adad
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2dc
0x34b655…2a6f
4 touches
1 conflict
0x9ccc60f5…00f3
0x34b655…2a6f
4 touches
1 conflict
0x298bc381…e223
0x34b655…2a6f
3 touches
1 conflict
0x32b804b3…ce18
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 0x8f2033941d…ebf2db
Audit this contract →
← previous block·next block →recent activity