← previous blocknext block →recent activity
Analyzing
Block #99,988,391
30 transactions · 22 stateful · 2026-08-28 20:01:56 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,988,391 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w215w020w122w223w325w426w427w529w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6426
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xfb14d7f1…e509
0x34b655…2a6f
6 touches
3 conflicts
0x4e12117e…d2cf
0x34b655…2a6f
6 touches
3 conflicts
0x736c304c…b89e
0xd32edf…ff58
5 touches
3 conflicts
0x6b267bdf…b173
0x34b655…2a6f
4 touches
1 conflict
0x31dc5296…bd23
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
6 conflicts on slot 0xc824469a90…af6426
Audit this contract →
← previous block·next block →recent activity