← previous blocknext block →recent activity
Analyzing
Block #83,356,261
20 transactions · 16 stateful · 2026-06-24 09:18:56 UTC
Parallelism
75/100
Blocked
44%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,356,261 · 20 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
1w02w14w05w06w17w28w311w012w415w118w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xb9b4eff6…c3ef
0x34b655…2a6f
6 touches
3 conflicts
0x97c67486…27fe
0x34b655…2a6f
6 touches
3 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x1ca68aab…5e4a
0x34b655…2a6f
4 touches
1 conflict
0x2154565b…be20
0x34b655…2a6f
4 touches
1 conflict
0x38351093…0a69
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity