← previous blocknext block →recent activity
Analyzing
Block #83,409,936
30 transactions · 27 stateful · 2026-06-24 15:17:41 UTC
Parallelism
70/100
Blocked
52%
Avg conflicts / tx
1.43
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,409,936 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w16w07w18w29w310w411w515w616w725w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0x967b4a40…7a78
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0xa1571d54…ae41
0x34b655…2a6f
12 touches
15 conflicts
0x1e00eb16…fb36
0x34b655…2a6f
12 touches
15 conflicts
0x9c7571b3…9605
0x34b655…2a6f
12 touches
15 conflicts
0x1c4d0ab3…3ce6
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 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
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity