← previous blocknext block →recent activity
Analyzing
Block #96,836,907
14 transactions · 13 stateful · 2026-08-17 17:34:25 UTC
Parallelism
50/100
Blocked
54%
Avg conflicts / tx
1.43
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,836,907 · 14 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
2w03w14w26w37w49w510w612w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xf9e23360…8ef7
0x34b655…2a6f
10 touches
10 conflicts
0xae085366…fa10
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xc2403164…b6d3
0x34b655…2a6f
5 touches
3 conflicts
0x366c7d57…0ed1
0x34b655…2a6f
4 touches
1 conflict
0x536f894b…2597
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