← previous blocknext block →recent activity
Analyzing
Block #99,320,110
18 transactions · 17 stateful · 2026-08-26 11:43:54 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,320,110 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w06w07w08w111w112w116w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe251ba03…50f8
0x34b655…2a6f
4 touches
1 conflict
0x251d1a45…0974
0x34b655…2a6f
4 touches
1 conflict
0x58a50018…5045
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
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
1 conflict on slot 0xe251ba03d8…af50f8
Audit this contract →
← previous block·next block →recent activity