← previous blocknext block →recent activity
Analyzing
Block #89,519,379
32 transactions · 31 stateful · 2026-07-22 23:17:40 UTC
Parallelism
78/100
Blocked
58%
Avg conflicts / tx
1.34
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #89,519,379 · 32 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w15w16w28w09w110w211w312w413w515w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xbd8eb6ad…9489
0xd32edf…ff58
9 touches
10 conflicts
0xba059816…a847
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x6b76ce29…0e84
0x34b655…2a6f
6 touches
3 conflicts
0x4acc8899…9b32
0x34b655…2a6f
4 touches
1 conflict
0x5c16527f…628c
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: 0x48cba278…e2b48b
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity