← previous blocknext block →recent activity
Analyzing
Block #96,557,105
7 transactions · 6 stateful · 2026-08-16 18:07:06 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,557,105 · 7 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
1w03w04w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xbc2236fb…8fca
0x34b655…2a6f
3 touches
1 conflict
0xdf147c8d…1b70
0x34b655…2a6f
3 touches
1 conflict
0x38c6ff01…689f
0x34b655…2a6f
2 touches
0 conflicts
0x3cf50d44…961b
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 0x9fd372a13e…ada959
Audit this contract →
← previous block·next block →recent activity