← previous blocknext block →recent activity
Analyzing
Block #89,562,508
21 transactions · 20 stateful · 2026-07-23 04:05:42 UTC
Parallelism
81/100
Blocked
55%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,562,508 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w06w17w28w19w210w312w213w014w116w218w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0006
0x0a2fbf…29b1
6 touches
3 conflicts
0x4d82bbb4…d6b4
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x55b4e430…44cb
0x754704…b603
6 touches
3 conflicts
0x03c6360e…f941
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
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity