← previous blocknext block →recent activity
Analyzing
Block #83,627,240
14 transactions · 14 stateful · 2026-06-25 15:27:54 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,627,240 · 14 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
1w02w16w08w19w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa9db7b4d…2957
0x40c49f…2af0
4 touches
1 conflict
0x2df5bd93…9e2d
0x34b655…2a6f
4 touches
1 conflict
0x758bd24b…cc0c
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xc7651488…e742
0x34b655…2a6f
4 touches
1 conflict
0xc978dec7…e3d6
0x34b655…2a6f
4 touches
1 conflict
0xd6d4eb00…30f3
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: 0x40c49f17…d22af0
1 conflict on slot 0xa9db7b4dd0…562957
Audit this contract →
← previous block·next block →recent activity