← previous blocknext block →recent activity
Analyzing
Block #87,593,114
36 transactions · 35 stateful · 2026-07-14 00:34:26 UTC
Parallelism
56/100
Blocked
57%
Avg conflicts / tx
3
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #87,593,114 · 36 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
1w02w03w14w27w08w19w010w111w012w113w214w315w418w719w820w921w1026w1132w1234w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0xa6b89ebb…a66e
0x34b655…2a6f
14 touches
21 conflicts
0xc8fec9ca…2d60
0x34b655…2a6f
12 touches
15 conflicts
0x4467ecee…e95b
0x34b655…2a6f
10 touches
10 conflicts
0xd2453506…54e4
0x34b655…2a6f
10 touches
10 conflicts
0xfd77e6c1…264b
0x34b655…2a6f
10 touches
10 conflicts
0x53bddbe8…2e5e
0x34b655…2a6f
8 touches
6 conflicts
0x7c524e26…54c6
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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity