← previous blocknext block →recent activity
Analyzing
Block #96,603,771
8 transactions · 8 stateful · 2026-08-16 22:01:50 UTC
Parallelism
50/100
Blocked
38%
Avg conflicts / tx
1.13
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,603,771 · 8 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f356c5d…bf12
0x34b655…2a6f
8 touches
6 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x4786839b…c29a
0x34b655…2a6f
4 touches
1 conflict
0xa3ed5a09…c6d3
0x34b655…2a6f
4 touches
1 conflict
0x81681867…64fa
0x34b655…2a6f
4 touches
1 conflict
0xf30b9357…2e1e
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 0x1f356c5d04…e0bf12
Audit this contract →
← previous block·next block →recent activity