← previous blocknext block →recent activity
Analyzing
Block #87,589,398
34 transactions · 30 stateful · 2026-07-14 00:09:35 UTC
Parallelism
59/100
Blocked
57%
Avg conflicts / tx
1.68
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #87,589,398 · 34 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w38w49w510w611w715w818w1120w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
14 touches
21 conflicts
0x63c900f4…2600
0x34b655…2a6f
14 touches
21 conflicts
0xad0c7701…1d83
0x34b655…2a6f
14 touches
21 conflicts
0xc2186704…5cc3
0x34b655…2a6f
14 touches
21 conflicts
0xdb7c435f…f490
0x34b655…2a6f
14 touches
21 conflicts
0x5170a218…3a84
0xc8689a…ee79
14 touches
21 conflicts
0x1ee4a6d2…6389
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