← previous blocknext block →recent activity
Analyzing
Block #87,918,359
115 transactions · 83 stateful · 2026-07-15 12:49:53 UTC
Parallelism
83/100
Blocked
82%
Avg conflicts / tx
3.15
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #87,918,359 · 115 txs across 20 waves · depth 20
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
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w413w320w421w227w564w665w767w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
28 touches
91 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
18 touches
36 conflicts
0x00000000…003d
0xa6afd3…d132
18 touches
36 conflicts
0x890a1db9…1712
0xa6afd3…d132
18 touches
36 conflicts
0x889d5e90…929a
0x2a68ba…90c5
18 touches
36 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
16 touches
28 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: 0x04fdeac2…f747d7
91 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity