← previous blocknext block →recent activity
Analyzing
Block #91,424,565
56 transactions · 46 stateful · 2026-07-29 19:15:45 UTC
Parallelism
73/100
Blocked
74%
Avg conflicts / tx
3.05
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #91,424,565 · 56 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w18w010w111w212w314w415w516w617w718w819w920w1031w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
22 touches
55 conflicts
0xac2a0273…721b
0x34b655…2a6f
20 touches
45 conflicts
0x737acb78…fce8
0x34b655…2a6f
20 touches
45 conflicts
0x1bf8d2af…d140
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xc0eb79d1…29a4
0x34b655…2a6f
10 touches
10 conflicts
0x772ab420…c2f6
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
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
55 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity