← previous blocknext block →recent activity
Analyzing
Block #83,399,722
46 transactions · 36 stateful · 2026-06-24 14:09:24 UTC
Parallelism
70/100
Blocked
64%
Avg conflicts / tx
2.2
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,399,722 · 46 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
1w02w13w04w06w07w19w110w211w113w214w320w021w122w223w324w425w526w627w728w829w930w1036w837w139w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
22 touches
55 conflicts
0x022f72c3…07b6
0xc8689a…ee79
14 touches
21 conflicts
0x9c7571b3…9605
0x34b655…2a6f
14 touches
21 conflicts
0xa1571d54…ae41
0x34b655…2a6f
14 touches
21 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
14 touches
21 conflicts
0xdf37a93d…879b
0x34b655…2a6f
14 touches
21 conflicts
0xc2ab3ad1…a6bc
0x34b655…2a6f
14 touches
21 conflicts
0xffc2f21e…b393
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
55 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity