← previous blocknext block →recent activity
Analyzing
Block #99,625,203
22 transactions · 19 stateful · 2026-08-27 13:26:54 UTC
Parallelism
77/100
Blocked
47%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,625,203 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w07w18w09w113w214w216w317w421w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f4e6c86…7789
0x34b655…2a6f
8 touches
6 conflicts
0x6c2f470e…3cf7
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x1f4e6c8652…177789
Audit this contract →
← previous block·next block →recent activity