← previous blocknext block →recent activity
Analyzing
Block #87,785,884
40 transactions · 36 stateful · 2026-07-14 22:03:50 UTC
Parallelism
70/100
Blocked
64%
Avg conflicts / tx
1.77
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #87,785,884 · 40 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w28w09w010w111w212w013w114w215w316w417w521w622w726w128w929w231w335w738w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xb96a99db…95aa
0x34b655…2a6f
8 touches
6 conflicts
0x2f675ab5…6407
0x34b655…2a6f
6 touches
3 conflicts
0x3fde350e…8d43
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity