← previous blocknext block →recent activity
Analyzing
Block #99,958,419
17 transactions · 12 stateful · 2026-08-28 17:30:56 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,958,419 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w19w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a548af5…0eb0
0x34b655…2a6f
8 touches
6 conflicts
0xed903df2…6ea4
0x34b655…2a6f
4 touches
1 conflict
0xf02bcd0d…9bb2
0x34b655…2a6f
4 touches
1 conflict
0x41dc0dc9…b241
0x34b655…2a6f
4 touches
1 conflict
0x9b15da5d…b284
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0x5a548af508…f00eb0
Audit this contract →
← previous block·next block →recent activity