← previous blocknext block →recent activity
Analyzing
Block #89,774,549
20 transactions · 14 stateful · 2026-07-24 00:30:40 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.25
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,774,549 · 20 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
1w06w17w09w010w111w215w117w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x3df7769a…5d17
0x3bd359…433a
4 touches
1 conflict
0x13dcc2b9…dfb6
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xff393f19…4dd2
0x0a3323…0a3c
4 touches
1 conflict
0x00000000…0000
0x0d73bf…be07
4 touches
1 conflict
0x00000000…0001
0x0d73bf…be07
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
1 conflict on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity