← previous blocknext block →recent activity
Analyzing
Block #96,706,588
11 transactions · 9 stateful · 2026-08-17 06:38:57 UTC
Parallelism
64/100
Blocked
44%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,706,588 · 11 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
1w05w16w27w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04f6d949…d859
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x966e45cf…0f25
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x198f3a22…7aeb
0x34b655…2a6f
2 touches
0 conflicts
0x72f34ca7…01c0
0x34b655…2a6f
2 touches
0 conflicts
0x77704719…12d9
0x34b655…2a6f
2 touches
0 conflicts
0x7c37629d…9e3f
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 0x04f6d949c9…eed859
Audit this contract →
← previous block·next block →recent activity