← previous blocknext block →recent activity
Analyzing
Block #87,705,026
37 transactions · 35 stateful · 2026-07-14 13:02:43 UTC
Parallelism
81/100
Blocked
60%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #87,705,026 · 37 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w17w28w410w011w112w213w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
14 touches
21 conflicts
0x00000000…0001
0xc1ff9f…b0fc
10 touches
10 conflicts
0x266d64d9…dc04
0xd32edf…ff58
9 touches
10 conflicts
0x56a919c4…ab49
0xee8c0e…1242
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
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
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity