← previous blocknext block →recent activity
Analyzing
Block #90,788,548
45 transactions · 36 stateful · 2026-07-27 13:53:10 UTC
Parallelism
69/100
Blocked
67%
Avg conflicts / tx
1.49
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #90,788,548 · 45 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w06w18w29w110w111w013w120w021w122w223w324w425w526w628w129w430w731w232w833w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x110a671c…e284
0x34b655…2a6f
10 touches
10 conflicts
0x9ca52d19…da85
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa4e3f209…ccab
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x08330b36…ae29
0x34b655…2a6f
6 touches
3 conflicts
0x0c33bb29…c6a9
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity