← previous blocknext block →recent activity
Analyzing
Block #83,665,339
22 transactions · 19 stateful · 2026-06-25 19:42:08 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
1.23
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,665,339 · 22 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
7w09w110w211w312w413w514w621w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa50fcb98…2b01
0x34b655…2a6f
12 touches
15 conflicts
0x157dbfb2…4089
0x34b655…2a6f
12 touches
15 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x06571461…d6f0
0x34b655…2a6f
10 touches
10 conflicts
0x6b47245e…a342
0x34b655…2a6f
10 touches
10 conflicts
0xe64e6363…e676
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0x478e6e08…83bf
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
15 conflicts on slot 0xa50fcb98bd…342b01
Audit this contract →
← previous block·next block →recent activity