← previous blocknext block →recent activity
Analyzing
Block #87,727,043
37 transactions · 35 stateful · 2026-07-14 15:30:13 UTC
Parallelism
65/100
Blocked
49%
Avg conflicts / tx
2.11
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,727,043 · 37 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w08w19w010w111w212w013w114w215w316w417w518w619w720w825w726w927w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0xafb8e71e…9285
0x34b655…2a6f
18 touches
36 conflicts
0x2c4e81fb…c4c8
0x34b655…2a6f
14 touches
21 conflicts
0x3b679ba3…b050
0x34b655…2a6f
14 touches
21 conflicts
0x767799cd…f423
0xc8689a…ee79
14 touches
21 conflicts
0x2bcdd4a1…3d3a
0x34b655…2a6f
14 touches
21 conflicts
0x921a58d1…db22
0x34b655…2a6f
14 touches
21 conflicts
0xaae6463e…bfcc
0x34b655…2a6f
14 touches
21 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