← previous blocknext block →recent activity
Analyzing
Block #99,207,664
18 transactions · 13 stateful · 2026-08-26 02:18:08 UTC
Parallelism
83/100
Blocked
23%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,207,664 · 18 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
6w010w111w213w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b2b7213…4899
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xaba6578d…bd48
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x9f651e91…056c
0xd32edf…ff58
3 touches
1 conflict
0x196c0976…dde4
0x34b655…2a6f
2 touches
0 conflicts
0x219c0a77…ccbd
0x34b655…2a6f
2 touches
0 conflicts
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 0x8b2b72134b…a34899
Audit this contract →
← previous block·next block →recent activity