← previous blocknext block →recent activity
Analyzing
Block #87,723,237
45 transactions · 33 stateful · 2026-07-14 15:04:44 UTC
Parallelism
67/100
Blocked
64%
Avg conflicts / tx
2.18
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #87,723,237 · 45 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w112w013w118w219w320w421w522w623w725w926w1027w1128w1231w1033w1135w1242w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0x64aaadbf…f9f3
0x34b655…2a6f
10 touches
10 conflicts
0x0dd44476…ef40
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x80fd3987…2314
0x34b655…2a6f
10 touches
10 conflicts
0x5170a218…3a84
0xc8689a…ee79
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xa0ebadea…4145
0x34b655…2a6f
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
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity