← previous blocknext block →recent activity
Analyzing
Block #99,857,402
22 transactions · 22 stateful · 2026-08-28 09:01:49 UTC
Parallelism
82/100
Blocked
32%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,857,402 · 22 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
1w05w18w09w110w211w212w315w016w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a26d4c4…d836
0x34b655…2a6f
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
4 touches
1 conflict
0xe124586e…e7b3
0x34b655…2a6f
4 touches
1 conflict
0xe3470554…335b
0x34b655…2a6f
4 touches
1 conflict
0xec2a8d79…70cb
0x34b655…2a6f
4 touches
1 conflict
0xfaf5fe80…1ffc
0x34b655…2a6f
4 touches
1 conflict
0x08db2444…22b2
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
3 conflicts on slot 0x9a26d4c414…e5d836
Audit this contract →
← previous block·next block →recent activity