← previous blocknext block →recent activity
Analyzing
Block #90,814,860
13 transactions · 13 stateful · 2026-07-27 16:05:38 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,814,860 · 13 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
3w06w17w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4bc1abab…5874
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0xbf6dac6c…96ba
0x34b655…2a6f
6 touches
3 conflicts
0x5c862b3a…8ef5
0x34b655…2a6f
4 touches
1 conflict
0x2a21b53a…211b
0x34b655…2a6f
4 touches
1 conflict
0x544eddd4…fb32
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
6 conflicts on slot 0x4bc1abab4b…a45874
Audit this contract →
← previous block·next block →recent activity