← previous blocknext block →recent activity
Analyzing
Block #87,518,318
33 transactions · 32 stateful · 2026-07-13 16:13:35 UTC
Parallelism
67/100
Blocked
66%
Avg conflicts / tx
2.64
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,518,318 · 33 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w28w39w010w111w212w313w414w515w616w717w818w920w121w424w526w728w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0006
0x0a2fbf…29b1
22 touches
55 conflicts
0x12265b62…e20d
0x0a2fbf…29b1
22 touches
55 conflicts
0x12265b62…e20e
0x0a2fbf…29b1
22 touches
55 conflicts
0x12265b62…e211
0x0a2fbf…29b1
22 touches
55 conflicts
0x00000000…0005
0x370e2e…63b4
22 touches
55 conflicts
0x1bff683e…7ecb
0x754704…b603
22 touches
55 conflicts
0x55b4e430…44cb
0x754704…b603
22 touches
55 conflicts
0x67e3455b…673c
0x0a2fbf…29b1
21 touches
55 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
55 conflicts on slot 0x0000000000…000006
Audit this contract →
← previous block·next block →recent activity