← previous blocknext block →recent activity
Analyzing
Block #99,133,138
28 transactions · 19 stateful · 2026-08-25 20:03:12 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,133,138 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w27w08w018w119w220w321w322w123w326w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xfac6b9b5…e982
0x065c9d…c394
5 touches
3 conflicts
0x248f83d1…63cf
0x34b655…2a6f
4 touches
1 conflict
0x33000c0a…82c3
0x34b655…2a6f
4 touches
1 conflict
0x5ce19b50…f20f
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity