← previous blocknext block →recent activity
Analyzing
Block #95,079,413
11 transactions · 8 stateful · 2026-08-11 13:59:14 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,079,413 · 11 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
1w05w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c2db8e9…fdc7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x2df6f59b…d662
0x34b655…2a6f
2 touches
0 conflicts
0x3f78072a…d0be
0x34b655…2a6f
2 touches
0 conflicts
0x48bfff05…d99e
0x34b655…2a6f
2 touches
0 conflicts
0x5bbda264…7dd0
0x34b655…2a6f
2 touches
0 conflicts
0x5bbda264…7dd1
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 0x2c2db8e9ef…f4fdc7
Audit this contract →
← previous block·next block →recent activity