← previous blocknext block →recent activity
Analyzing
Block #96,532,314
11 transactions · 8 stateful · 2026-08-16 16:02:25 UTC
Parallelism
55/100
Blocked
63%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,532,314 · 11 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
2w05w16w27w38w410w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb67df4fa…af6d
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xa4c56761…79e0
0x34b655…2a6f
6 touches
3 conflicts
0x3bdd71a2…b6eb
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…aaff
0x34b655…2a6f
4 touches
1 conflict
0x5b37bb6b…ab00
0x34b655…2a6f
4 touches
1 conflict
0x69411fb3…e36d
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
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 0xb67df4fa4a…71af6d
Audit this contract →
← previous block·next block →recent activity