← previous blocknext block →recent activity
Analyzing
Block #90,800,473
43 transactions · 36 stateful · 2026-07-27 14:53:10 UTC
Parallelism
60/100
Blocked
72%
Avg conflicts / tx
2.84
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #90,800,473 · 43 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w16w17w28w39w010w011w115w016w117w218w319w420w521w627w1128w1229w1330w1432w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0xa3f6f7c8…2436
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x41377979…0a18
0x34b655…2a6f
10 touches
10 conflicts
0xc6000ba5…8d65
0x34b655…2a6f
10 touches
10 conflicts
0x94bb14fe…8f47
0x34b655…2a6f
10 touches
10 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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity