← previous blocknext block →recent activity
Analyzing
Block #96,785,486
21 transactions · 20 stateful · 2026-08-17 13:15:47 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,785,486 · 21 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
1w02w03w04w05w18w09w112w215w316w417w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2840c278…bbc7
0x34b655…2a6f
6 touches
3 conflicts
0x855b4bf7…313e
0x34b655…2a6f
6 touches
3 conflicts
0xcd51eb25…31f9
0x34b655…2a6f
6 touches
3 conflicts
0x9e7f288e…1a24
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x948836ff…59ab
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 0x2840c278a3…01bbc7
Audit this contract →
← previous block·next block →recent activity