← previous blocknext block →recent activity
Analyzing
Block #90,789,968
42 transactions · 34 stateful · 2026-07-27 14:00:19 UTC
Parallelism
64/100
Blocked
71%
Avg conflicts / tx
2.43
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #90,789,968 · 42 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w08w19w212w013w114w215w316w417w518w619w720w821w923w324w425w1026w129w330w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
20 touches
45 conflicts
0xbf78ee7f…e7fd
0x34b655…2a6f
14 touches
21 conflicts
0xf2f4727d…cdb7
0x34b655…2a6f
10 touches
10 conflicts
0x007892de…5752
0x34b655…2a6f
10 touches
10 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x917f99a5…7989
0x34b655…2a6f
6 touches
3 conflicts
0x96c36734…b2e3
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
45 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity