← previous blocknext block →recent activity
Analyzing
Block #99,882,300
23 transactions · 20 stateful · 2026-08-28 11:07:19 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,882,300 · 23 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
2w04w16w211w012w113w214w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e5cc219…8e87
0x34b655…2a6f
8 touches
6 conflicts
0x2c2351f5…3c1a
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x01a10ea5…b9d1
0x34b655…2a6f
4 touches
1 conflict
0xccebf5c5…8758
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
0x34b655…2a6f
4 touches
1 conflict
0x928caaa5…5974
0x34b655…2a6f
4 touches
1 conflict
0x953517cb…cdec
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 0x9e5cc21992…6c8e87
Audit this contract →
← previous block·next block →recent activity