← previous blocknext block →recent activity
Analyzing
Block #90,978,005
48 transactions · 39 stateful · 2026-07-28 05:46:22 UTC
Parallelism
71/100
Blocked
56%
Avg conflicts / tx
1.54
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #90,978,005 · 48 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
1w02w05w16w07w18w211w012w113w015w116w221w022w124w225w327w428w130w531w632w733w641w742w843w944w1046w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0x5fe7e126…6dd2
0x34b655…2a6f
10 touches
10 conflicts
0xe8eae8a3…bacc
0x34b655…2a6f
8 touches
6 conflicts
0x5571e830…9cea
0x34b655…2a6f
6 touches
3 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7e1faa73…bfbf
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity