← previous blocknext block →recent activity
Analyzing
Block #83,465,889
13 transactions · 12 stateful · 2026-06-24 21:31:28 UTC
Parallelism
46/100
Blocked
58%
Avg conflicts / tx
1.62
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,465,889 · 13 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
1w02w15w06w17w28w39w410w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xf86f15cd…38af
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0xdf37a93d…879b
0x34b655…2a6f
10 touches
10 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
10 touches
10 conflicts
0x9e7c6b67…7db2
0x34b655…2a6f
8 touches
6 conflicts
0x2f3e5a3b…b31b
0x34b655…2a6f
4 touches
1 conflict
0xfdfa79dc…7700
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity