← previous blocknext block →recent activity
Analyzing
Block #83,665,056
16 transactions · 15 stateful · 2026-06-25 19:40:16 UTC
Parallelism
69/100
Blocked
40%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,665,056 · 16 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
4w05w17w08w19w210w312w414w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37a276a3…673f
0x34b655…2a6f
8 touches
6 conflicts
0x4c9b58ba…6a2e
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xec71d7fa…def3
0x34b655…2a6f
6 touches
3 conflicts
0x3c051cd1…3276
0x34b655…2a6f
4 touches
1 conflict
0x615b2995…a788
0x34b655…2a6f
4 touches
1 conflict
0x71391185…0caa
0x34b655…2a6f
4 touches
1 conflict
0x75291f8b…3ac0
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 0x37a276a33f…0f673f
Audit this contract →
← previous block·next block →recent activity