← previous blocknext block →recent activity
Analyzing
Block #99,957,357
25 transactions · 24 stateful · 2026-08-28 17:25:35 UTC
Parallelism
84/100
Blocked
29%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,957,357 · 25 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
2w03w04w06w18w19w212w213w114w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a548af5…0eb0
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x513d59c7…1fa5
0x34b655…2a6f
4 touches
1 conflict
0x85bfd0af…ce96
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
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