← previous blocknext block →recent activity
Analyzing
Block #83,627,910
42 transactions · 32 stateful · 2026-06-25 15:32:23 UTC
Parallelism
71/100
Blocked
63%
Avg conflicts / tx
2.17
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #83,627,910 · 42 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w18w29w310w411w012w118w019w120w221w322w423w524w625w726w827w928w1029w1134w140w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
24 touches
66 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0xff4ee2c4…6e5e
0x34b655…2a6f
10 touches
10 conflicts
0x0835adb5…ad83
0x34b655…2a6f
9 touches
10 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
8 touches
6 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
8 touches
6 conflicts
0x8e5cc690…b06b
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
66 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity