← previous blocknext block →recent activity
Analyzing
Block #83,659,049
37 transactions · 30 stateful · 2026-06-25 19:00:15 UTC
Parallelism
60/100
Blocked
73%
Avg conflicts / tx
2.62
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #83,659,049 · 37 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w17w28w310w014w115w216w317w418w519w620w721w822w923w1024w1125w1234w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
22 touches
55 conflicts
0xda7f9bd2…e332
0x34b655…2a6f
16 touches
28 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
10 touches
10 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x3cf50d44…961b
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
55 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity