← previous blocknext block →recent activity
Analyzing
Block #96,119,966
9 transactions · 8 stateful · 2026-08-15 05:28:08 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,119,966 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xa47b7766…ee6e
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc967ff68…3fb0
0x34b655…2a6f
4 touches
1 conflict
0x7f4a8466…f2cc
0x2b46c0…1669
2 touches
0 conflicts
0x03ce1783…8d3f
0x34b655…2a6f
2 touches
0 conflicts
0x04263be6…a20e
0x34b655…2a6f
2 touches
0 conflicts
0x2006bbe4…04dc
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 0x7de579746e…f0f5ba
Audit this contract →
← previous block·next block →recent activity