← previous blocknext block →recent activity
Analyzing
Block #99,780,122
16 transactions · 15 stateful · 2026-08-28 02:30:37 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,780,122 · 16 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
1w04w05w16w27w311w413w115w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb682e7d…dde9
0x34b655…2a6f
8 touches
6 conflicts
0xc2f61d99…8418
0x34b655…2a6f
4 touches
1 conflict
0xdbd9d618…7b7f
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x0221091a…da2a
0x34b655…2a6f
4 touches
1 conflict
0x107b89e4…470d
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 0xfb682e7d8c…dcdde9
Audit this contract →
← previous block·next block →recent activity