← previous blocknext block →recent activity
Analyzing
Block #96,017,160
21 transactions · 15 stateful · 2026-08-14 20:51:03 UTC
Parallelism
86/100
Blocked
53%
Avg conflicts / tx
0.62
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,017,160 · 21 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
1w02w19w110w011w212w013w114w115w216w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31616f97…1acc
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xb9a63764…f004
0x34b655…2a6f
6 touches
3 conflicts
0xafb29fba…c9c2
0xd32edf…ff58
5 touches
3 conflicts
0x1bdb47ec…864a
0x34b655…2a6f
4 touches
1 conflict
0x0e391a2e…d634
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x48b13e5e…3c2a
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
3 conflicts on slot 0x31616f9701…df1acc
Audit this contract →
← previous block·next block →recent activity