← previous blocknext block →recent activity
Analyzing
Block #84,488,237
35 transactions · 31 stateful · 2026-06-29 15:07:11 UTC
Parallelism
77/100
Blocked
68%
Avg conflicts / tx
1.91
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,488,237 · 35 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w713w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
16 touches
28 conflicts
0x835b7ef7…35c7
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0xd59f6ed1…03e8
0x1b6862…e19c
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: 0xd637b38f…c64160
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity