← previous blocknext block →recent activity
Analyzing
Block #90,372,002
31 transactions · 29 stateful · 2026-07-26 02:49:54 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
2.13
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #90,372,002 · 31 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w19w211w312w413w514w615w716w817w919w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1110ff7d…d969
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
16 touches
28 conflicts
0xd0fd6c76…ddaf
0x34b655…2a6f
12 touches
15 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xb15c58ec…bd83
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
36 conflicts on slot 0x1110ff7de7…c9d969
Audit this contract →
← previous block·next block →recent activity