← previous blocknext block →recent activity
Analyzing
Block #87,920,252
44 transactions · 38 stateful · 2026-07-15 13:02:33 UTC
Parallelism
70/100
Blocked
66%
Avg conflicts / tx
2.07
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #87,920,252 · 44 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w210w312w013w114w015w116w217w318w419w520w622w223w328w531w334w438w743w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xc1ff9f…b0fc
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x5d863b2f…bd28
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x449d101e…ea3f
0xa6afd3…d132
8 touches
6 conflicts
0x0fffa5c0…a3a9
0xa6afd3…d132
8 touches
6 conflicts
0x94ba9c4a…41d8
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: 0xc1ff9fef…f4b0fc
21 conflicts on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity