← previous blocknext block →recent activity
Analyzing
Block #89,856,737
10 transactions · 9 stateful · 2026-07-24 07:25:15 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,856,737 · 10 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
2w05w06w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x9db3090e…7fb8
0x34b655…2a6f
4 touches
1 conflict
0x32181e64…29ee
0x34b655…2a6f
4 touches
1 conflict
0xd4230a60…bd13
0x34b655…2a6f
4 touches
1 conflict
0xd68cd74f…9826
0x34b655…2a6f
4 touches
1 conflict
0x2840c278…bbc7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x2b0aa8f5…b903
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 0x0f2d78b1bb…5e7363
Audit this contract →
← previous block·next block →recent activity