← previous blocknext block →recent activity
Analyzing
Block #83,571,372
16 transactions · 16 stateful · 2026-06-25 09:14:54 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,571,372 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w19w212w014w115w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d61a1c5…9fe6
0x34b655…2a6f
6 touches
3 conflicts
0x12c6929d…e7db
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0xd16df6cd…5532
0x40c49f…2af0
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
2 touches
0 conflicts
0xc23ae4f2…40a9
0x065c9d…c394
2 touches
0 conflicts
0xc5253a62…23a3
0x065c9d…c394
2 touches
0 conflicts
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 0x1d61a1c583…bf9fe6
Audit this contract →
← previous block·next block →recent activity