← previous blocknext block →recent activity
Analyzing
Block #96,663,615
25 transactions · 23 stateful · 2026-08-17 03:02:49 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,663,615 · 25 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
1w02w03w15w110w111w012w013w014w119w220w121w222w323w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe2ca9bf2…8da8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0x01e7b865…6e6e
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb80
0x1b6862…e19c
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity