← previous blocknext block →recent activity
Analyzing
Block #99,248,916
22 transactions · 19 stateful · 2026-08-26 05:45:41 UTC
Parallelism
73/100
Blocked
47%
Avg conflicts / tx
0.59
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,248,916 · 22 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
2w04w05w16w18w29w313w415w016w117w118w121w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b2b7213…4899
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x32a831f5…6884
0x34b655…2a6f
4 touches
1 conflict
0xabf6f441…13c8
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
6 conflicts on slot 0x8b2b72134b…a34899
Audit this contract →
← previous block·next block →recent activity