← previous blocknext block →recent activity
Analyzing
Block #99,587,234
29 transactions · 25 stateful · 2026-08-27 10:11:43 UTC
Parallelism
86/100
Blocked
20%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,587,234 · 29 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
1w03w16w07w18w09w015w217w328w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62023181…811e
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x57e6562d…e4b1
0x34b655…2a6f
4 touches
1 conflict
0x7146f910…de2b
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x96ed54e2…04ed
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
3 conflicts on slot 0x6202318167…4d811e
Audit this contract →
← previous block·next block →recent activity