← previous blocknext block →recent activity
Analyzing
Block #96,837,375
14 transactions · 13 stateful · 2026-08-17 17:36:46 UTC
Parallelism
57/100
Blocked
54%
Avg conflicts / tx
1.36
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,837,375 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w26w27w38w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x216ffe66…1f94
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x81ca8c9e…28cb
0x34b655…2a6f
6 touches
3 conflicts
0xe2b988ac…37d8
0x34b655…2a6f
6 touches
3 conflicts
0x7bf1c03f…c440
0x34b655…2a6f
4 touches
1 conflict
0x9c2fc330…0091
0x34b655…2a6f
4 touches
1 conflict
0xac3e4969…39e9
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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity