← previous blocknext block →recent activity
Analyzing
Block #83,399,371
43 transactions · 37 stateful · 2026-06-24 14:07:04 UTC
Parallelism
67/100
Blocked
65%
Avg conflicts / tx
2.07
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,399,371 · 43 txs across 14 waves · depth 14
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
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w06w17w29w010w111w112w013w114w215w316w420w322w423w524w635w136w237w838w939w1040w1141w1242w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x758bd24b…cc0c
0x34b655…2a6f
10 touches
10 conflicts
0xf6b29666…46d2
0xd32edf…ff58
9 touches
10 conflicts
0xcb45d9d6…cb86
0x1b6862…e19c
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001e
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: Perpl
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity