← previous blocknext block →recent activity
Analyzing
Block #83,636,419
18 transactions · 17 stateful · 2026-06-25 16:29:15 UTC
Parallelism
72/100
Blocked
35%
Avg conflicts / tx
0.78
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,636,419 · 18 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
1w02w13w04w16w27w38w412w017w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3405238a…68b6
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xcd63138b…63d9
0x34b655…2a6f
6 touches
3 conflicts
0x7fe97198…79ab
0x34b655…2a6f
4 touches
1 conflict
0x811cb01f…e507
0x34b655…2a6f
4 touches
1 conflict
0x866bd8f8…9cd7
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0x91fcd19a…29f6
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
10 conflicts on slot 0x3405238a6d…6268b6
Audit this contract →
← previous block·next block →recent activity