← previous blocknext block →recent activity
Analyzing
Block #83,356,192
24 transactions · 19 stateful · 2026-06-24 09:18:28 UTC
Parallelism
79/100
Blocked
37%
Avg conflicts / tx
0.46
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,356,192 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w29w010w111w212w114w018w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xfb4cb196…8c4a
0x34b655…2a6f
6 touches
3 conflicts
0xe5a38e46…a68c
0x34b655…2a6f
6 touches
3 conflicts
0x07bb3f5a…617e
0x34b655…2a6f
4 touches
1 conflict
0x15086f36…c164
0x34b655…2a6f
4 touches
1 conflict
0x4c04ce68…d007
0x34b655…2a6f
4 touches
1 conflict
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0x80630fb9…a436
0x34b655…2a6f
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
3 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity