← previous blocknext block →recent activity
Analyzing
Block #87,519,676
38 transactions · 34 stateful · 2026-07-13 16:22:46 UTC
Parallelism
50/100
Blocked
79%
Avg conflicts / tx
5.05
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #87,519,676 · 38 txs across 19 waves · depth 19
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
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w28w29w312w413w014w115w216w317w418w533w536w237w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
38 touches
171 conflicts
0x25e96430…6236
0x0a2fbf…29b1
38 touches
171 conflicts
0x25e96430…6237
0x0a2fbf…29b1
38 touches
171 conflicts
0x25e96430…623a
0x0a2fbf…29b1
38 touches
171 conflicts
0x55b4e430…44cb
0x754704…b603
38 touches
171 conflicts
0x5f5467c2…5948
0x0a2fbf…29b1
36 touches
153 conflicts
0x00000000…0005
0x370e2e…63b4
36 touches
153 conflicts
0x1bff683e…7ecb
0x754704…b603
36 touches
153 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: 0x0a2fbf2d…f729b1
171 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity