← previous blocknext block →recent activity
Analyzing
Block #89,536,090
14 transactions · 12 stateful · 2026-07-23 01:09:12 UTC
Parallelism
86/100
Blocked
25%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,536,090 · 14 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
2w04w05w06w17w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x63da8263…7a24
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x14ea9ada…e627
0x34b655…2a6f
2 touches
0 conflicts
0x14ea9ada…e628
0x34b655…2a6f
2 touches
0 conflicts
0x14ea9ada…e62c
0x34b655…2a6f
2 touches
0 conflicts
0x21f41d0b…8b28
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 0x63da8263b5…587a24
Audit this contract →
← previous block·next block →recent activity