← previous blocknext block →recent activity
Analyzing
Block #90,810,387
19 transactions · 17 stateful · 2026-07-27 15:43:05 UTC
Parallelism
79/100
Blocked
41%
Avg conflicts / tx
0.74
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,810,387 · 19 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
1w02w14w25w06w19w211w315w317w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc6000ba5…8d65
0x34b655…2a6f
8 touches
6 conflicts
0xbc25e327…a1ca
0x34b655…2a6f
8 touches
6 conflicts
0xe56c2492…47ca
0x34b655…2a6f
6 touches
3 conflicts
0x64158499…e370
0x34b655…2a6f
6 touches
3 conflicts
0x6bdb9869…7558
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x8c8774b6…40b9
0x34b655…2a6f
6 touches
3 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: Perpl
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity