← previous blocknext block →recent activity
Analyzing
Block #83,866,055
39 transactions · 37 stateful · 2026-06-26 18:01:28 UTC
Parallelism
82/100
Blocked
62%
Avg conflicts / tx
1.49
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,866,055 · 39 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
1w02w13w14w05w26w27w08w09w110w011w112w213w314w415w518w122w125w333w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
12 touches
15 conflicts
0x0cef6110…dc83
0xd32edf…ff58
11 touches
15 conflicts
0xcb45d9d6…cb80
0x1b6862…e19c
10 touches
10 conflicts
0x90a9e3f8…17ab
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0018
0x1b6862…e19c
10 touches
10 conflicts
0x2d5c395b…6b5a
0xa6afd3…d132
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
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity