← previous blocknext block →recent activity
Analyzing
Block #84,510,805
41 transactions · 35 stateful · 2026-06-29 17:37:48 UTC
Parallelism
73/100
Blocked
77%
Avg conflicts / tx
2.2
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #84,510,805 · 41 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w28w39w410w411w512w530w531w634w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x3be9f29a…c293
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0002
0xd637b3…4160
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x6e2becf4…0c5f
0x34b655…2a6f
8 touches
6 conflicts
0x7c6d3d6d…9deb
0x34b655…2a6f
8 touches
6 conflicts
0x94710b77…a921
0x34b655…2a6f
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity