← previous blocknext block →recent activity
Analyzing
Block #87,707,058
48 transactions · 40 stateful · 2026-07-14 13:16:20 UTC
Parallelism
67/100
Blocked
70%
Avg conflicts / tx
2.04
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,707,058 · 48 txs across 16 waves · depth 16
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
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w17w28w39w010w111w012w114w217w018w119w220w321w422w523w631w332w435w336w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xc5031114…58ac
0x34b655…2a6f
12 touches
15 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
10 touches
10 conflicts
0x1fd19887…8e0e
0x34b655…2a6f
10 touches
10 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
10 touches
10 conflicts
0x767799cd…f423
0xc8689a…ee79
10 touches
10 conflicts
0x030bd256…c5c3
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity