← previous blocknext block →recent activity
Analyzing
Block #96,604,039
23 transactions · 21 stateful · 2026-08-16 22:03:11 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
0.91
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,604,039 · 23 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
2w03w04w15w26w07w18w09w310w412w413w515w620w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x02991b41…19e6
0x34b655…2a6f
8 touches
6 conflicts
0xda46a376…f6a6
0x34b655…2a6f
8 touches
6 conflicts
0x2aab0897…78f7
0x34b655…2a6f
4 touches
1 conflict
0x6366e366…b51c
0x34b655…2a6f
4 touches
1 conflict
0x68d3db4e…f6da
0x34b655…2a6f
4 touches
1 conflict
0x720bad39…0419
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity