← previous blocknext block →recent activity
Analyzing
Block #83,637,416
20 transactions · 16 stateful · 2026-06-25 16:35:55 UTC
Parallelism
70/100
Blocked
44%
Avg conflicts / tx
0.6
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,637,416 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w010w111w212w116w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99c320a0…b4a8
0x34b655…2a6f
8 touches
6 conflicts
0xe45981a9…165a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x369a11e2…566f
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x5d25b21e…1d1c
0x34b655…2a6f
4 touches
1 conflict
0x6ebf28cd…0c35
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
6 conflicts on slot 0x99c320a0a0…feb4a8
Audit this contract →
← previous block·next block →recent activity