← previous blocknext block →recent activity
Analyzing
Block #87,787,379
18 transactions · 16 stateful · 2026-07-14 22:13:50 UTC
Parallelism
61/100
Blocked
69%
Avg conflicts / tx
1.61
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,787,379 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w08w210w311w412w114w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f461725…5ab2
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
8 touches
6 conflicts
0xb241a755…fdca
0x34b655…2a6f
8 touches
6 conflicts
0x347e7e76…914b
0x34b655…2a6f
8 touches
6 conflicts
0x9ae859db…2d84
0x34b655…2a6f
8 touches
6 conflicts
0x97a61672…8c43
0x34b655…2a6f
8 touches
6 conflicts
0x59dccbd8…2bf6
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
10 conflicts on slot 0x2f4617255d…ea5ab2
Audit this contract →
← previous block·next block →recent activity