← previous blocknext block →recent activity
Analyzing
Block #99,020,122
10 transactions · 9 stateful · 2026-08-25 10:29:41 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,020,122 · 10 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4de5db4e…eec2
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x0221091a…da2a
0x34b655…2a6f
2 touches
0 conflicts
0x0a9d9c98…d0e0
0x34b655…2a6f
2 touches
0 conflicts
0x18d2f762…4068
0x34b655…2a6f
2 touches
0 conflicts
0x1fe7644e…513c
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
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 0x4de5db4e5a…57eec2
Audit this contract →
← previous block·next block →recent activity