← previous blocknext block →recent activity
Analyzing
Block #96,664,231
14 transactions · 11 stateful · 2026-08-17 03:05:55 UTC
Parallelism
64/100
Blocked
45%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,664,231 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w18w29w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f9fe384…1402
0x34b655…2a6f
6 touches
3 conflicts
0x14fe1598…d0ba
0x34b655…2a6f
4 touches
1 conflict
0x1a5d321d…a474
0x34b655…2a6f
4 touches
1 conflict
0x21170416…c384
0x34b655…2a6f
4 touches
1 conflict
0x3a9e59a0…6198
0x34b655…2a6f
4 touches
1 conflict
0x3f0a88e0…392e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x607e481f…43e3
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 0x7f9fe3845a…611402
Audit this contract →
← previous block·next block →recent activity