← previous blocknext block →recent activity
Analyzing
Block #96,702,328
14 transactions · 9 stateful · 2026-08-17 06:17:31 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,702,328 · 14 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
1w07w18w29w312w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c602697…299d
0x34b655…2a6f
6 touches
3 conflicts
0xe3abe489…ebf3
0x77d53b…8080
4 touches
1 conflict
0xf63c2a2b…bc60
0x34b655…2a6f
4 touches
1 conflict
0x0fd2cbc5…476b
0x77d53b…8080
4 touches
1 conflict
0x9f2cccee…48d2
0x77d53b…8080
4 touches
1 conflict
0x29a945df…bcd8
0x34b655…2a6f
4 touches
1 conflict
0x2de9863d…96dc
0x34b655…2a6f
4 touches
1 conflict
0x315e07b8…9823
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
3 conflicts on slot 0x2c60269724…f6299d
Audit this contract →
← previous block·next block →recent activity