← previous blocknext block →recent activity
Analyzing
Block #99,778,641
26 transactions · 23 stateful · 2026-08-28 02:23:07 UTC
Parallelism
77/100
Blocked
39%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,778,641 · 26 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
1w02w13w06w17w08w210w112w213w316w419w120w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5150abbe…43c3
0x34b655…2a6f
10 touches
10 conflicts
0x230d0904…a656
0x34b655…2a6f
6 touches
3 conflicts
0xa9d11061…b7e9
0x34b655…2a6f
6 touches
3 conflicts
0xc3ece2a4…2dce
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1045386d…cb8c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
10 conflicts on slot 0x5150abbe56…e443c3
Audit this contract →
← previous block·next block →recent activity