← previous blocknext block →recent activity
Analyzing
Block #83,661,249
34 transactions · 28 stateful · 2026-06-25 19:14:54 UTC
Parallelism
74/100
Blocked
54%
Avg conflicts / tx
1.38
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,661,249 · 34 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
1w02w03w16w17w28w39w215w016w117w018w119w220w321w422w523w632w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x37a276a3…673f
0x34b655…2a6f
12 touches
15 conflicts
0x68e821ac…5930
0xd32edf…ff58
7 touches
6 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity