← previous blocknext block →recent activity
Analyzing
Block #83,624,419
36 transactions · 34 stateful · 2026-06-25 15:09:05 UTC
Parallelism
56/100
Blocked
59%
Avg conflicts / tx
3.67
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #83,624,419 · 36 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w38w09w110w211w312w413w514w615w716w817w918w1019w1120w1221w1322w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
30 touches
105 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
26 touches
78 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
24 touches
66 conflicts
0x022f72c3…07b6
0xc8689a…ee79
24 touches
66 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
24 touches
66 conflicts
0xffc2f21e…b393
0x34b655…2a6f
20 touches
45 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x2faddb92…b54e
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
105 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity