← previous blocknext block →recent activity
Analyzing
Block #87,920,011
38 transactions · 32 stateful · 2026-07-15 13:00:56 UTC
Parallelism
71/100
Blocked
75%
Avg conflicts / tx
1.95
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #87,920,011 · 38 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
1w02w13w06w17w08w19w010w113w014w115w217w318w419w520w621w722w224w428w529w630w731w232w234w736w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0xc1ff9f…b0fc
16 touches
28 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
12 touches
15 conflicts
0xa3f6f7c8…2436
0x34b655…2a6f
10 touches
10 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x165b3a0d…8987
0x34b655…2a6f
8 touches
6 conflicts
0x41377979…0a18
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
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
28 conflicts on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity