← previous blocknext block →recent activity
Analyzing
Block #96,436,039
10 transactions · 8 stateful · 2026-08-16 07:57:53 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,436,039 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4230a60…bd13
0x34b655…2a6f
4 touches
1 conflict
0x19439a65…eb51
0x34b655…2a6f
4 touches
1 conflict
0x2021fb2a…d63b
0x34b655…2a6f
4 touches
1 conflict
0x2021fb2a…d63c
0x34b655…2a6f
4 touches
1 conflict
0x2592d715…a50e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x827c091a…d3d2
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
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
1 conflict on slot 0xd4230a6034…58bd13
Audit this contract →
← previous block·next block →recent activity