← previous blocknext block →recent activity
Analyzing
Block #95,394,434
17 transactions · 15 stateful · 2026-08-12 16:36:31 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,394,434 · 17 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
2w05w06w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x3bfb282e…7419
0xd32edf…ff58
3 touches
1 conflict
0xd6c26f16…d86a
0x34b655…2a6f
3 touches
1 conflict
0x0a6e0609…1966
0x188d58…ea8e
2 touches
0 conflicts
0x0a6e0609…1968
0x188d58…ea8e
2 touches
0 conflicts
0x7a86e227…01f8
0x188d58…ea8e
2 touches
0 conflicts
0x7a86e227…01f9
0x188d58…ea8e
2 touches
0 conflicts
0x7a86e227…01fb
0x188d58…ea8e
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity