← previous blocknext block →recent activity
Analyzing
Block #96,665,561
7 transactions · 6 stateful · 2026-08-17 03:12:36 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,665,561 · 7 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
1w02w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67a56c8b…f955
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf1345bef…5530
0x34b655…2a6f
4 touches
1 conflict
0x0431e51f…6f91
0x34b655…2a6f
2 touches
0 conflicts
0x0490581d…adaf
0x34b655…2a6f
2 touches
0 conflicts
0x070f03d7…b8a3
0x34b655…2a6f
2 touches
0 conflicts
0x1a439162…b838
0x34b655…2a6f
2 touches
0 conflicts
0x1c22eb60…d3e2
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 0x67a56c8b2e…d7f955
Audit this contract →
← previous block·next block →recent activity