← previous blocknext block →recent activity
Analyzing
Block #89,770,470
21 transactions · 19 stateful · 2026-07-24 00:10:04 UTC
Parallelism
90/100
Blocked
32%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #89,770,470 · 21 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
1w02w13w04w07w08w19w012w113w116w017w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x8047e9b2…9bb8
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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: 0x63e48b72…8c53f2
1 conflict on slot 0x0000000000…000004
Audit this contract →
← previous block·next block →recent activity