← previous blocknext block →recent activity
Analyzing
Block #96,548,176
10 transactions · 9 stateful · 2026-08-16 17:22:12 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,548,176 · 10 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
1w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x342fc7e5…c7c7
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0728ec77…146c
0x34b655…2a6f
4 touches
1 conflict
0xcc06b563…c7fc
0x34b655…2a6f
4 touches
1 conflict
0x163d1c74…5a12
0x34b655…2a6f
4 touches
1 conflict
0x30d58b0b…8806
0x34b655…2a6f
4 touches
1 conflict
0x808aff35…5c6f
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 0x342fc7e56d…45c7c7
Audit this contract →
← previous block·next block →recent activity