← previous blocknext block →recent activity
Analyzing
Block #96,509,045
10 transactions · 9 stateful · 2026-08-16 14:05:24 UTC
Parallelism
30/100
Blocked
67%
Avg conflicts / tx
2.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,509,045 · 10 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w47w58w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x9a3463f0…0b73
0x34b655…2a6f
8 touches
6 conflicts
0x0460135c…98fd
0x34b655…2a6f
8 touches
6 conflicts
0xea1b8c07…b969
0x34b655…2a6f
6 touches
3 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x7ef4ba09…2a25
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity