← previous blocknext block →recent activity
Analyzing
Block #89,517,338
17 transactions · 14 stateful · 2026-07-22 23:04:02 UTC
Parallelism
65/100
Blocked
43%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #89,517,338 · 17 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
3w04w15w26w09w211w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x20d0c78a…d1ae
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x02d895f0…2b93
0x34b655…2a6f
4 touches
1 conflict
0x908408b4…9e64
0x34b655…2a6f
4 touches
1 conflict
0x9a36cb2e…0929
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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 0x20d0c78aaa…2ad1ae
Audit this contract →
← previous block·next block →recent activity