← previous blocknext block →recent activity
Analyzing
Block #84,357,706
37 transactions · 31 stateful · 2026-06-29 00:37:00 UTC
Parallelism
86/100
Blocked
55%
Avg conflicts / tx
1.03
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,357,706 · 37 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w28w39w010w111w212w319w020w121w222w323w427w228w335w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa1eb8469…d895
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xd637b3…4160
8 touches
6 conflicts
0x25f3de4a…87b5
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c1
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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: Perpl
10 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity