← previous blocknext block →recent activity
Analyzing
Block #90,889,277
6 transactions · 6 stateful · 2026-07-27 22:20:01 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
0.67
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #90,889,277 · 6 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62b26c37…87d6
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x20d87ce7…4436
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x35b0198e…3e0d
0x34b655…2a6f
6 touches
3 conflicts
0x8c2d84f9…cb2e
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
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
3 conflicts on slot 0x62b26c37ec…fb87d6
Audit this contract →
← previous block·next block →recent activity