← previous blocknext block →recent activity
Analyzing
Block #87,731,650
37 transactions · 33 stateful · 2026-07-14 16:01:01 UTC
Parallelism
51/100
Blocked
67%
Avg conflicts / tx
2.35
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #87,731,650 · 37 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w16w07w18w29w012w114w215w316w417w518w619w722w1023w1128w1329w1430w332w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0x147259c6…1709
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xa55c4598…2988
0x34b655…2a6f
10 touches
10 conflicts
0x0dd44476…ef40
0x34b655…2a6f
10 touches
10 conflicts
0xc8536f01…eb88
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity