← previous blocknext block →recent activity
Analyzing
Block #87,791,878
20 transactions · 18 stateful · 2026-07-14 22:43:55 UTC
Parallelism
35/100
Blocked
67%
Avg conflicts / tx
2.15
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,791,878 · 20 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w58w69w710w813w914w1016w1118w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x04a566e1…26f3
0x34b655…2a6f
12 touches
15 conflicts
0x98834cc0…6c23
0x34b655…2a6f
12 touches
15 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x28c62bca…b746
0x34b655…2a6f
10 touches
10 conflicts
0xb59b0c85…f36c
0x34b655…2a6f
9 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
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
15 conflicts on slot 0x04a566e1fd…f826f3
Audit this contract →
← previous block·next block →recent activity