← previous blocknext block →recent activity
Analyzing
Block #83,889,318
41 transactions · 34 stateful · 2026-06-26 20:36:37 UTC
Parallelism
78/100
Blocked
50%
Avg conflicts / tx
1.56
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,889,318 · 41 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
5w06w17w28w39w410w529w535w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0x5da4ed2f…283f
0xa6afd3…d132
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0xc05b880b…7746
0xa6afd3…d132
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0xe02484a6…c32e
0xc8689a…ee79
10 touches
10 conflicts
0x1e346a85…e9c5
0x34b655…2a6f
10 touches
10 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
10 touches
10 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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity