← previous blocknext block →recent activity
Analyzing
Block #89,377,932
15 transactions · 13 stateful · 2026-07-22 07:32:26 UTC
Parallelism
60/100
Blocked
46%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,377,932 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w110w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721c
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x6e19c9a0…7d86
0x34b655…2a6f
4 touches
1 conflict
0x82109f73…b6a1
0x34b655…2a6f
4 touches
1 conflict
0xff9c8b2d…bda7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity