← previous blocknext block →recent activity
Analyzing
Block #83,493,253
16 transactions · 13 stateful · 2026-06-25 00:33:54 UTC
Parallelism
81/100
Blocked
46%
Avg conflicts / tx
0.63
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,493,253 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w16w29w010w111w212w013w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xf5310ef7…485a
0x40c49f…2af0
4 touches
1 conflict
0xa02e5cdd…76b8
0x34b655…2a6f
4 touches
1 conflict
0xb6acec9c…ea53
0x34b655…2a6f
4 touches
1 conflict
0xba070ab6…4be4
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd2453506…54e4
0x34b655…2a6f
4 touches
1 conflict
0xfe39a1f7…8eb0
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