← previous blocknext block →recent activity
Analyzing
Block #90,891,471
13 transactions · 12 stateful · 2026-07-27 22:31:04 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,891,471 · 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
5w06w17w28w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41377979…0a18
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xa3834f05…a4cf
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0xd97c2fdb…27d5
0x34b655…2a6f
4 touches
1 conflict
0x3f867ff8…dfbc
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
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 0x413779793d…8f0a18
Audit this contract →
← previous block·next block →recent activity