← previous blocknext block →recent activity
Analyzing
Block #89,743,321
13 transactions · 13 stateful · 2026-07-23 21:52:59 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.46
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,743,321 · 13 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
1w03w14w05w06w17w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x632634ca…a410
0x0a2fbf…29b1
4 touches
1 conflict
0x632634ca…a411
0x0a2fbf…29b1
4 touches
1 conflict
0x632634ca…a414
0x0a2fbf…29b1
4 touches
1 conflict
0xcad6f82c…cca6
0x0a2fbf…29b1
4 touches
1 conflict
0xcad6f82c…cca7
0x0a2fbf…29b1
4 touches
1 conflict
0x55b4e430…44cb
0x754704…b603
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity