← previous blocknext block →recent activity
Analyzing
Block #95,746,285
7 transactions · 7 stateful · 2026-08-13 22:08:09 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,746,285 · 7 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
3w04w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5a1b2fe…5369
0x34b655…2a6f
4 touches
1 conflict
0xe8eae8a3…bacc
0x34b655…2a6f
4 touches
1 conflict
0x4efae872…6aa8
0x34b655…2a6f
4 touches
1 conflict
0x22cf1403…46f3
0x34b655…2a6f
2 touches
0 conflicts
0x312c6e56…3d7a
0x34b655…2a6f
2 touches
0 conflicts
0x43274fb7…08aa
0x34b655…2a6f
2 touches
0 conflicts
0x6939e474…4256
0x34b655…2a6f
2 touches
0 conflicts
0x6a95ba16…0c9e
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 0xc5a1b2febf…f05369
Audit this contract →
← previous block·next block →recent activity