← previous blocknext block →recent activity
Analyzing
Block #99,850,529
20 transactions · 19 stateful · 2026-08-28 08:27:07 UTC
Parallelism
50/100
Blocked
58%
Avg conflicts / tx
2.3
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,850,529 · 20 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w37w48w510w612w713w815w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22f10271…841d
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x9d7f7621…97de
0x34b655…2a6f
8 touches
6 conflicts
0xbc0de6fd…ea8d
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x15698ac9…2a46
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0x22f10271ce…96841d
Audit this contract →
← previous block·next block →recent activity