← previous blocknext block →recent activity
Analyzing
Block #99,934,407
28 transactions · 25 stateful · 2026-08-28 15:29:55 UTC
Parallelism
75/100
Blocked
36%
Avg conflicts / tx
0.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #99,934,407 · 28 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
2w03w14w06w17w210w111w216w320w423w527w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x898a1a2f…bf47
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x6fce7a05…d778
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc16e646d…4fb0
0x34b655…2a6f
4 touches
1 conflict
0xc7954a60…d294
0x34b655…2a6f
4 touches
1 conflict
0xcc78fa71…852c
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 0x898a1a2f48…fabf47
Audit this contract →
← previous block·next block →recent activity