← previous blocknext block →recent activity
Analyzing
Block #89,574,083
21 transactions · 20 stateful · 2026-07-23 05:23:05 UTC
Parallelism
81/100
Blocked
30%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #89,574,083 · 21 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
4w06w17w18w212w213w014w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0302b0d6…64c8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xe772a49f…2f96
0x0a2fbf…29b1
4 touches
1 conflict
0xe772a49f…2f99
0x0a2fbf…29b1
4 touches
1 conflict
0xf7c0889e…ecb9
0x0a2fbf…29b1
4 touches
1 conflict
0xf7c0889e…ecba
0x0a2fbf…29b1
4 touches
1 conflict
0x1ce5dbf8…958d
0x34b655…2a6f
4 touches
1 conflict
0x2e52db7c…3141
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 0x0302b0d62b…9d64c8
Audit this contract →
← previous block·next block →recent activity