← previous blocknext block →recent activity
Analyzing
Block #83,656,025
44 transactions · 33 stateful · 2026-06-25 18:40:05 UTC
Parallelism
68/100
Blocked
64%
Avg conflicts / tx
2.05
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,656,025 · 44 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w27w19w216w017w121w122w223w324w425w526w627w731w1032w1134w1237w1340w241w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
22 touches
55 conflicts
0xe6fd65c0…3a8a
0x34b655…2a6f
14 touches
21 conflicts
0x2050abfb…45e8
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0xf8716a36…8787
0x34b655…2a6f
10 touches
10 conflicts
0xd064a456…b881
0x34b655…2a6f
10 touches
10 conflicts
0xe46a9e83…22b5
0x34b655…2a6f
10 touches
10 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
10 touches
10 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
55 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity