← previous blocknext block →recent activity
Analyzing
Block #83,614,813
39 transactions · 34 stateful · 2026-06-25 14:04:49 UTC
Parallelism
62/100
Blocked
59%
Avg conflicts / tx
2.26
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #83,614,813 · 39 txs across 15 waves · depth 15
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w27w111w012w113w214w315w416w517w618w726w331w833w1034w1135w1236w1337w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
18 touches
36 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xffc2f21e…b393
0x34b655…2a6f
12 touches
15 conflicts
0x6fbc2e5a…e69c
0x34b655…2a6f
8 touches
6 conflicts
0x74fd0a9b…3aaa
0x34b655…2a6f
8 touches
6 conflicts
0x9e4890bd…fd9d
0x34b655…2a6f
8 touches
6 conflicts
0x8e507257…71c1
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
36 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity