← previous blocknext block →recent activity
Analyzing
Block #89,747,476
21 transactions · 17 stateful · 2026-07-23 22:13:57 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #89,747,476 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w08w111w115w219w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc371d7e3…d732
0x34b655…2a6f
6 touches
3 conflicts
0x213ee207…a151
0x2b46c0…1669
4 touches
1 conflict
0x46279ae7…20dd
0x2b46c0…1669
4 touches
1 conflict
0x53e50026…6d8c
0x2b46c0…1669
4 touches
1 conflict
0x7f4a8466…f2cc
0x2b46c0…1669
4 touches
1 conflict
0x32409e80…a396
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x758a0dd5…0f46
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 0xc371d7e333…acd732
Audit this contract →
← previous block·next block →recent activity