← previous blocknext block →recent activity
Analyzing
Block #87,593,056
38 transactions · 32 stateful · 2026-07-14 00:34:03 UTC
Parallelism
55/100
Blocked
66%
Avg conflicts / tx
2.26
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,593,056 · 38 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w111w112w213w314w415w516w617w718w819w922w323w1024w1126w1229w1334w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x4c188934…158e
0x34b655…2a6f
16 touches
28 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
14 touches
21 conflicts
0x34d95d94…3a16
0x34b655…2a6f
12 touches
15 conflicts
0x53bddbe8…2e5e
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
12 touches
15 conflicts
0x167de262…f61f
0x34b655…2a6f
12 touches
15 conflicts
0x2fade833…5de4
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity