← previous blocknext block →recent activity
Analyzing
Block #90,893,395
69 transactions · 43 stateful · 2026-07-27 22:40:44 UTC
Parallelism
77/100
Blocked
67%
Avg conflicts / tx
1.94
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #90,893,395 · 69 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w012w013w015w016w120w221w325w431w032w134w235w337w438w540w643w144w245w349w350w457w1060w1165w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0x889d5e90…929a
0x2a68ba…90c5
16 touches
28 conflicts
0x40970e69…da50
0x2b46c0…1669
14 touches
21 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
14 touches
21 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
14 touches
21 conflicts
0xdb067026…9eb8
0x2b46c0…1669
14 touches
21 conflicts
0x5778d110…d2e6
0xc8689a…ee79
14 touches
21 conflicts
0x66a11a3b…0ee9
0xa6afd3…d132
14 touches
21 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