← previous blocknext block →recent activity
Analyzing
Block #96,598,810
10 transactions · 7 stateful · 2026-08-16 21:36:53 UTC
Parallelism
70/100
Blocked
29%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,598,810 · 10 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
4w05w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4188cc5f…2d2e
0x34b655…2a6f
6 touches
3 conflicts
0xcfce8a0c…c8c7
0x34b655…2a6f
4 touches
1 conflict
0x784eaad2…d176
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x1bd67185…1acb
0x34b655…2a6f
3 touches
1 conflict
0x4acc6dca…a868
0x34b655…2a6f
2 touches
0 conflicts
0x4c86d0e4…e2f1
0x34b655…2a6f
2 touches
0 conflicts
0x4c86d0e4…e2f2
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
3 conflicts on slot 0x4188cc5f13…782d2e
Audit this contract →
← previous block·next block →recent activity