← previous blocknext block →recent activity
Analyzing
Block #96,355,160
14 transactions · 12 stateful · 2026-08-16 01:11:07 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,355,160 · 14 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
1w02w15w08w19w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xf5ea108a…dbf6
0x34b655…2a6f
4 touches
1 conflict
0x000bde1a…e123
0x34b655…2a6f
2 touches
0 conflicts
0x785c87ba…a0f1
0x34b655…2a6f
2 touches
0 conflicts
0x9c2fc330…0091
0x34b655…2a6f
2 touches
0 conflicts
0xe131df52…7554
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 0x6d1b72eefe…416b78
Audit this contract →
← previous block·next block →recent activity