← previous blocknext block →recent activity
Analyzing
Block #95,594,182
67 transactions · 65 stateful · 2026-08-13 09:22:02 UTC
Parallelism
97/100
Blocked
2%
Avg conflicts / tx
0.01
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,594,182 · 67 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37eae3e2…7724
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
2 touches
0 conflicts
0x08636046…e60f
0x34b655…2a6f
2 touches
0 conflicts
0x0b87c899…c0f9
0x34b655…2a6f
2 touches
0 conflicts
0x30c5329c…711c
0x34b655…2a6f
2 touches
0 conflicts
0x3cbfa5aa…cc9b
0x34b655…2a6f
2 touches
0 conflicts
0x5e78c401…7a7e
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 0x37eae3e2b5…fc7724
Audit this contract →
← previous block·next block →recent activity