← previous blocknext block →recent activity
Analyzing
Block #90,791,317
23 transactions · 20 stateful · 2026-07-27 14:07:06 UTC
Parallelism
74/100
Blocked
40%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,791,317 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w09w110w212w013w315w116w017w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc3d5171…8357
0x34b655…2a6f
8 touches
6 conflicts
0xbb322930…ace5
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x93b6fab0…09d6
0x34b655…2a6f
8 touches
6 conflicts
0x6d6b897d…da00
0x34b655…2a6f
6 touches
3 conflicts
0x48e3acd8…cf41
0x34b655…2a6f
6 touches
3 conflicts
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xfc3d51716d…008357
Audit this contract →
← previous block·next block →recent activity