← previous blocknext block →recent activity
Analyzing
Block #99,160,910
20 transactions · 20 stateful · 2026-08-25 22:22:55 UTC
Parallelism
75/100
Blocked
30%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,160,910 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w19w010w111w214w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0xbd590df7…9891
0x34b655…2a6f
8 touches
6 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
6 touches
3 conflicts
0xbbe823d1…efae
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
4 touches
1 conflict
0x5ecbbe42…e861
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
10 conflicts on slot 0xe1c4e5ce15…770dec
Audit this contract →
← previous block·next block →recent activity