← previous blocknext block →recent activity
Analyzing
Block #90,237,164
17 transactions · 16 stateful · 2026-07-25 15:24:29 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,237,164 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w18w29w210w315w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d2de0f6…e6c6
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe04e9d60…bbef
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x09396f14…669f
0x34b655…2a6f
4 touches
1 conflict
0x1a7adb59…a2c8
0x34b655…2a6f
4 touches
1 conflict
0x2ead5a0b…3978
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 0x0d2de0f636…8fe6c6
Audit this contract →
← previous block·next block →recent activity