← previous blocknext block →recent activity
Analyzing
Block #87,785,669
44 transactions · 37 stateful · 2026-07-14 22:02:24 UTC
Parallelism
61/100
Blocked
70%
Avg conflicts / tx
3.05
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #87,785,669 · 44 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
1w03w04w19w110w011w012w114w116w217w318w419w520w621w722w823w924w1025w1126w1227w1328w1431w232w233w342w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
30 touches
105 conflicts
0xa80684c9…3948
0x34b655…2a6f
12 touches
15 conflicts
0x20ff72d4…5971
0x34b655…2a6f
12 touches
15 conflicts
0x5170a218…3a84
0xc8689a…ee79
12 touches
15 conflicts
0xf3fbc9b8…ab58
0x34b655…2a6f
12 touches
15 conflicts
0x63c900f4…2600
0x34b655…2a6f
12 touches
15 conflicts
0x5b145de0…367c
0xc8689a…ee79
10 touches
10 conflicts
0x28c62bca…b746
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
105 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity