← previous blocknext block →recent activity
Analyzing
Block #99,369,119
8 transactions · 8 stateful · 2026-08-26 15:50:44 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,369,119 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf06fce24…887d
0x34b655…2a6f
4 touches
1 conflict
0xf8906758…2ece
0x34b655…2a6f
4 touches
1 conflict
0x172b0de5…980b
0x34b655…2a6f
4 touches
1 conflict
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x1b3f5f5c…64c2
0x34b655…2a6f
2 touches
0 conflicts
0x70e677f5…e3bd
0x34b655…2a6f
2 touches
0 conflicts
0x7de57974…f5ba
0x34b655…2a6f
2 touches
0 conflicts
0x9ad325f5…cc43
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xf06fce24b3…55887d
Audit this contract →
← previous block·next block →recent activity