← previous blocknext block →recent activity
Analyzing
Block #89,857,369
9 transactions · 8 stateful · 2026-07-24 07:28:25 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,857,369 · 9 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
2w03w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f0fe1df…da89
0x34b655…2a6f
4 touches
1 conflict
0x2f0fe1df…da8a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x94a77fc9…7577
0x34b655…2a6f
4 touches
1 conflict
0x9db3090e…7fb8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd1ed88c7…be83
0x34b655…2a6f
3 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 0x2f0fe1df2e…3ada89
Audit this contract →
← previous block·next block →recent activity