← previous blocknext block →recent activity
Analyzing
Block #95,086,748
14 transactions · 12 stateful · 2026-08-11 14:36:08 UTC
Parallelism
64/100
Blocked
67%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,086,748 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w27w28w39w410w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5bc53470…8dde
0x34b655…2a6f
8 touches
6 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x0d2de0f6…e6c6
0x34b655…2a6f
4 touches
1 conflict
0xc24bdf76…c59b
0x34b655…2a6f
4 touches
1 conflict
0x7b42f6a7…f49c
0x34b655…2a6f
4 touches
1 conflict
0x88bca116…a51e
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
6 conflicts on slot 0x5bc534701b…af8dde
Audit this contract →
← previous block·next block →recent activity