← previous blocknext block →recent activity
Analyzing
Block #83,843,104
35 transactions · 30 stateful · 2026-06-26 15:28:20 UTC
Parallelism
77/100
Blocked
53%
Avg conflicts / tx
1.49
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,843,104 · 35 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w512w113w014w115w216w317w418w519w620w725w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0xffc2f21e…b393
0x34b655…2a6f
10 touches
10 conflicts
0x95e8fb7c…67d2
0xd32edf…ff58
9 touches
10 conflicts
0xe2e45419…f17b
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
8 touches
6 conflicts
0x8726ff39…3be8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
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: Perpl
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity