← previous blocknext block →recent activity
Analyzing
Block #90,803,794
14 transactions · 13 stateful · 2026-07-27 15:09:53 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,803,794 · 14 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
1w02w03w15w06w110w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe3471350…0bcf
0x34b655…2a6f
6 touches
3 conflicts
0x11cff9e3…14b2
0x34b655…2a6f
4 touches
1 conflict
0x1c106a56…de20
0x34b655…2a6f
4 touches
1 conflict
0x20ff72d4…5971
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x344bc09a…942f
0x34b655…2a6f
4 touches
1 conflict
0x40d7b52a…09ff
0x34b655…2a6f
4 touches
1 conflict
0x55cf4758…265c
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 0xe347135026…5b0bcf
Audit this contract →
← previous block·next block →recent activity