← previous blocknext block →recent activity
Analyzing
Block #99,779,541
11 transactions · 11 stateful · 2026-08-28 02:27:41 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,779,541 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w07w18w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe226a0be…c046
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x274a8f8b…3603
0x34b655…2a6f
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xd2b36119…e4e1
0x851145…3f07
4 touches
1 conflict
0xa70cb615…11da
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
1 conflict on slot 0xe226a0be4d…4bc046
Audit this contract →
← previous block·next block →recent activity