← previous blocknext block →recent activity
Analyzing
Block #83,641,335
59 transactions · 46 stateful · 2026-06-25 17:02:05 UTC
Parallelism
66/100
Blocked
83%
Avg conflicts / tx
3.81
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #83,641,335 · 59 txs across 20 waves · depth 20
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
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w29w311w413w014w115w216w317w418w519w621w722w846w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
28 touches
91 conflicts
0x00000000…0002
0xaa7ee7…f0e4
18 touches
36 conflicts
0xffb1ee54…7c2c
0x34b655…2a6f
15 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
14 touches
21 conflicts
0x37a276a3…673f
0x34b655…2a6f
12 touches
15 conflicts
0x0b408000…9df1
0x34b655…2a6f
12 touches
15 conflicts
0xda5e0705…ecb9
0x34b655…2a6f
12 touches
15 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