← previous blocknext block →recent activity
Analyzing
Block #99,119,389
22 transactions · 20 stateful · 2026-08-25 18:54:02 UTC
Parallelism
86/100
Blocked
45%
Avg conflicts / tx
0.59
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,119,389 · 22 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
2w03w14w26w27w08w19w113w014w117w218w221w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5a7d7c6…e138
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x30ae635d…5e67
0x34b655…2a6f
4 touches
1 conflict
0x3fcb5bac…74b8
0x34b655…2a6f
4 touches
1 conflict
0x49028f08…fcc8
0x34b655…2a6f
4 touches
1 conflict
0x5202eeec…466f
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
3 conflicts on slot 0xe5a7d7c607…8be138
Audit this contract →
← previous block·next block →recent activity