← previous blocknext block →recent activity
Analyzing
Block #87,596,337
41 transactions · 29 stateful · 2026-07-14 00:56:00 UTC
Parallelism
59/100
Blocked
62%
Avg conflicts / tx
1.41
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,596,337 · 41 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
4w07w08w19w216w317w418w519w620w721w822w923w1027w134w1235w1336w1437w1538w16
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xc2186704…5cc3
0x34b655…2a6f
8 touches
6 conflicts
0xd379a368…fea4
0x34b655…2a6f
8 touches
6 conflicts
0xfd77e6c1…264b
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0xa241f0f0…ca94
0x34b655…2a6f
8 touches
6 conflicts
0xa6b89ebb…a66e
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity