← previous blocknext block →recent activity
Analyzing
Block #87,792,508
17 transactions · 16 stateful · 2026-07-14 22:48:08 UTC
Parallelism
53/100
Blocked
63%
Avg conflicts / tx
2.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #87,792,508 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8d989c17…e984
0x34b655…2a6f
16 touches
28 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x28c62bca…b746
0x34b655…2a6f
14 touches
21 conflicts
0x5b145de0…367c
0xc8689a…ee79
14 touches
21 conflicts
0x9ae859db…2d84
0x34b655…2a6f
14 touches
21 conflicts
0x9fd37234…2731
0x34b655…2a6f
14 touches
21 conflicts
0x21c9fd73…dae4
0x34b655…2a6f
14 touches
21 conflicts
0x40a81b78…095d
0x34b655…2a6f
12 touches
15 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
28 conflicts on slot 0x8d989c177f…b7e984
Audit this contract →
← previous block·next block →recent activity