← previous blocknext block →recent activity
Analyzing
Block #89,703,536
22 transactions · 17 stateful · 2026-07-23 18:32:04 UTC
Parallelism
91/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,703,536 · 22 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
1w02w17w08w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0x7e7e48fd…94c8
0xd32edf…ff58
3 touches
1 conflict
0x729c91b8…9538
0x188d58…ea8e
2 touches
0 conflicts
0x729c91b8…953a
0x188d58…ea8e
2 touches
0 conflicts
0xeb392325…18b2
0x188d58…ea8e
2 touches
0 conflicts
0xeb392325…18b3
0x188d58…ea8e
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 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity