← previous blocknext block →recent activity
Analyzing
Block #89,279,787
33 transactions · 25 stateful · 2026-07-21 20:36:28 UTC
Parallelism
88/100
Blocked
40%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,279,787 · 33 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
6w07w18w211w012w116w017w018w120w221w322w124w329w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x042d7533…0599
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x48cba2…b48b
6 touches
3 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x0be747d5…22e0
0x34b655…2a6f
4 touches
1 conflict
0x0be747d5…22e1
0x34b655…2a6f
4 touches
1 conflict
0x265c227d…afa6
0x34b655…2a6f
4 touches
1 conflict
0x3d2e7bcf…54f9
0x34b655…2a6f
4 touches
1 conflict
0x4ac4de26…a5c8
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
3 conflicts on slot 0x042d7533ef…2c0599
Audit this contract →
← previous block·next block →recent activity