← previous blocknext block →recent activity
Analyzing
Block #83,853,328
35 transactions · 30 stateful · 2026-06-26 16:36:34 UTC
Parallelism
74/100
Blocked
70%
Avg conflicts / tx
2.03
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,853,328 · 35 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w39w410w511w625w429w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x90a9e3f8…17ab
0x34b655…2a6f
10 touches
10 conflicts
0x2d5c395b…6b5a
0xa6afd3…d132
10 touches
10 conflicts
0x7c5260f4…bd96
0xa6afd3…d132
10 touches
10 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
8 touches
6 conflicts
0xdb067026…9eb8
0x69df8a…6292
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
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity