← previous blocknext block →recent activity
Analyzing
Block #90,787,885
100 transactions · 87 stateful · 2026-07-27 13:49:50 UTC
Parallelism
77/100
Blocked
83%
Avg conflicts / tx
4.54
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #90,787,885 · 100 txs across 23 waves · depth 23
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
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w27w38w09w110w211w312w413w514w515w616w725w459w665w767w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x48cba2…b48b
32 touches
120 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x889d5e90…929a
0x2a68ba…90c5
20 touches
45 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…003d
0xa6afd3…d132
18 touches
36 conflicts
0x0dd44476…ef40
0x34b655…2a6f
16 touches
28 conflicts
0x1a4fb69e…7136
0xa6afd3…d132
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
16 touches
28 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
120 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity