← previous blocknext block →recent activity
Analyzing
Block #87,711,132
37 transactions · 30 stateful · 2026-07-14 13:43:36 UTC
Parallelism
65/100
Blocked
63%
Avg conflicts / tx
2.16
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,711,132 · 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
3w04w16w08w09w113w014w115w216w317w418w519w620w721w822w923w1029w234w1136w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0x55c2c22c…0474
0x34b655…2a6f
10 touches
10 conflicts
0x8fe37a3f…4c89
0x34b655…2a6f
8 touches
6 conflicts
0x214fb529…3f33
0x34b655…2a6f
6 touches
3 conflicts
0x4560e5a8…b741
0x34b655…2a6f
6 touches
3 conflicts
0x67905f6e…02a1
0x34b655…2a6f
6 touches
3 conflicts
0x5b145de0…367c
0xc8689a…ee79
6 touches
3 conflicts
0x097b4de6…ed0c
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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity