← previous blocknext block →recent activity
Analyzing
Block #90,795,114
40 transactions · 39 stateful · 2026-07-27 14:26:12 UTC
Parallelism
55/100
Blocked
72%
Avg conflicts / tx
3.15
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #90,795,114 · 40 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w27w38w49w010w111w212w313w414w515w616w717w818w919w1020w1124w226w331w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0xe9452241…95a3
0x34b655…2a6f
12 touches
15 conflicts
0x24eaf46d…8c2e
0x34b655…2a6f
12 touches
15 conflicts
0x7aad02c6…b979
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x48cba2…b48b
10 touches
10 conflicts
0xadd9c687…1f8b
0x34b655…2a6f
8 touches
6 conflicts
0xf75c3485…6028
0x34b655…2a6f
8 touches
6 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