← previous blocknext block →recent activity
Analyzing
Block #90,785,504
22 transactions · 18 stateful · 2026-07-27 13:37:49 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,785,504 · 22 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
1w02w17w08w112w013w014w115w216w319w020w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa4df566b…a510
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x379dc435…6616
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0x394c3833…b4a9
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x53d6f1c9…16c4
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 0xa4df566b55…23a510
Audit this contract →
← previous block·next block →recent activity