← previous blocknext block →recent activity
Analyzing
Block #83,617,293
51 transactions · 33 stateful · 2026-06-25 14:21:24 UTC
Parallelism
71/100
Blocked
73%
Avg conflicts / tx
2.29
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #83,617,293 · 51 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
1w02w16w09w110w211w314w015w116w217w318w419w520w621w722w823w924w1025w1126w1230w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
28 touches
91 conflicts
0xc2dcae88…f07a
0x34b655…2a6f
10 touches
10 conflicts
0x1e346a85…e9c5
0x34b655…2a6f
10 touches
10 conflicts
0xab981df1…2941
0x34b655…2a6f
10 touches
10 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
8 touches
6 conflicts
0x8eb5f632…c9eb
0x34b655…2a6f
8 touches
6 conflicts
0x9fbabe09…8dd6
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
91 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity