← previous blocknext block →recent activity
Analyzing
Block #96,665,898
7 transactions · 7 stateful · 2026-08-17 03:14:18 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,665,898 · 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
1w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xd79c9727…1233
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x0bfc83e5…e8eb
0x34b655…2a6f
2 touches
0 conflicts
0x2dfcc03e…8aa0
0x34b655…2a6f
2 touches
0 conflicts
0x40414c4b…b1cc
0x34b655…2a6f
2 touches
0 conflicts
0x48d5c98c…0ebc
0x34b655…2a6f
2 touches
0 conflicts
0x4c619b7d…f4fa
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity