← previous blocknext block →recent activity
Analyzing
Block #99,120,621
21 transactions · 17 stateful · 2026-08-25 19:00:14 UTC
Parallelism
90/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,120,621 · 21 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w014w120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3286eb19…11dc
0x34b655…2a6f
4 touches
1 conflict
0x676207a8…5d7e
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xa02838a3…bc54
0x34b655…2a6f
4 touches
1 conflict
0xe8dc3d55…2657
0xd32edf…ff58
3 touches
1 conflict
0x09beabbc…065d
0x188d58…ea8e
2 touches
0 conflicts
0x46cb45de…a566
0x188d58…ea8e
2 touches
0 conflicts
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
1 conflict on slot 0x3286eb19b9…da11dc
Audit this contract →
← previous block·next block →recent activity