← previous blocknext block →recent activity
Analyzing
Block #89,528,329
11 transactions · 10 stateful · 2026-07-23 00:17:26 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,528,329 · 11 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
4w05w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56b5f5c0…a3ad
0x34b655…2a6f
4 touches
1 conflict
0x9c1bbfa8…9931
0x34b655…2a6f
4 touches
1 conflict
0xa77cc9c9…2d1f
0x34b655…2a6f
4 touches
1 conflict
0xc9cafc31…3505
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x102b4d1a…6d88
0x40c49f…2af0
2 touches
0 conflicts
0x1653de0f…cccc
0x40c49f…2af0
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 0x56b5f5c03e…07a3ad
Audit this contract →
← previous block·next block →recent activity