← previous blocknext block →recent activity
Analyzing
Block #99,869,806
24 transactions · 21 stateful · 2026-08-28 10:04:23 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,869,806 · 24 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
1w05w06w08w09w110w212w114w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad213752…f193
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x1df57ac9…922f
0x34b655…2a6f
4 touches
1 conflict
0x21a1d259…eda5
0x34b655…2a6f
4 touches
1 conflict
0x34a323bc…7b17
0x34b655…2a6f
4 touches
1 conflict
0x953517cb…cdec
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc66f747c…aad0
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 0xad2137521e…73f193
Audit this contract →
← previous block·next block →recent activity