← previous blocknext block →recent activity
Analyzing
Block #87,641,139
17 transactions · 15 stateful · 2026-07-14 05:55:31 UTC
Parallelism
59/100
Blocked
73%
Avg conflicts / tx
2.06
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,641,139 · 17 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
1w02w13w24w35w48w39w410w515w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5a3b1be…8122
0x34b655…2a6f
14 touches
21 conflicts
0x3c0c2f32…c3df
0x34b655…2a6f
10 touches
10 conflicts
0x4560e5a8…b741
0x34b655…2a6f
10 touches
10 conflicts
0x49f75237…44f4
0x34b655…2a6f
10 touches
10 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x7837c02d…0965
0x34b655…2a6f
10 touches
10 conflicts
0x8d4c0bb9…ccd3
0x34b655…2a6f
10 touches
10 conflicts
0x9599eb41…b5d6
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0xb5a3b1be7c…288122
Audit this contract →
← previous block·next block →recent activity