← previous blocknext block →recent activity
Analyzing
Block #90,774,542
26 transactions · 20 stateful · 2026-07-27 12:42:41 UTC
Parallelism
85/100
Blocked
40%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,774,542 · 26 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
1w02w13w17w011w112w215w119w220w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a005879…de60
0x34b655…2a6f
8 touches
6 conflicts
0x7032dc14…49ea
0x34b655…2a6f
6 touches
3 conflicts
0xc62600db…b34c
0xd32edf…ff58
5 touches
3 conflicts
0x62dbeb4d…a388
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd6
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x93b6fab0…09d6
0x34b655…2a6f
4 touches
1 conflict
0x95d625be…d84b
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 0x0a005879f3…a5de60
Audit this contract →
← previous block·next block →recent activity