← previous blocknext block →recent activity
Analyzing
Block #99,981,293
15 transactions · 15 stateful · 2026-08-28 19:26:08 UTC
Parallelism
60/100
Blocked
53%
Avg conflicts / tx
0.93
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,981,293 · 15 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
2w04w16w07w18w29w310w411w112w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcc8f826…7c5f
0x34b655…2a6f
10 touches
10 conflicts
0xffaa25f5…1528
0x34b655…2a6f
8 touches
6 conflicts
0xca2b4ab7…5236
0x34b655…2a6f
8 touches
6 conflicts
0x82312d8c…bc80
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xdc8d7edd…8a03
0x34b655…2a6f
6 touches
3 conflicts
0x5fad6fee…7714
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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
10 conflicts on slot 0xfcc8f826d7…5f7c5f
Audit this contract →
← previous block·next block →recent activity