← previous blocknext block →recent activity
Analyzing
Block #95,128,668
23 transactions · 22 stateful · 2026-08-11 18:07:01 UTC
Parallelism
70/100
Blocked
59%
Avg conflicts / tx
1.57
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,128,668 · 23 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w17w28w39w410w318w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa56e54d0…2d39
0x34b655…2a6f
12 touches
15 conflicts
0x4c188934…158e
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x50afedcd…91cc
0x34b655…2a6f
4 touches
1 conflict
0x536588d3…19c5
0x34b655…2a6f
4 touches
1 conflict
0x78b7945b…2113
0x34b655…2a6f
4 touches
1 conflict
0x7a14fba5…3918
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0xa56e54d018…f82d39
Audit this contract →
← previous block·next block →recent activity