← previous blocknext block →recent activity
Analyzing
Block #89,404,786
27 transactions · 25 stateful · 2026-07-22 10:32:01 UTC
Parallelism
93/100
Blocked
4%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,404,786 · 27 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
2w023w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31519d10…f76b
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x680ca7d7…2df4
0x34b655…2a6f
4 touches
1 conflict
0x07e025a5…0279
0x065c9d…c394
2 touches
0 conflicts
0x21ed48b8…7dee
0x065c9d…c394
2 touches
0 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
2 touches
0 conflicts
0x80f8832c…35cc
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x31519d107d…60f76b
Audit this contract →
← previous block·next block →recent activity