← previous blocknext block →recent activity
Analyzing
Block #83,456,102
32 transactions · 28 stateful · 2026-06-24 20:26:05 UTC
Parallelism
78/100
Blocked
61%
Avg conflicts / tx
1.31
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,456,102 · 32 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
1w02w13w14w26w27w38w49w010w011w112w113w014w115w216w317w418w519w622w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0xe6950848…9ff6
0x34b655…2a6f
8 touches
6 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
8 touches
6 conflicts
0x8d0e1d29…cd3e
0x34b655…2a6f
8 touches
6 conflicts
0x55e45a2d…f86c
0xd32edf…ff58
7 touches
6 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity