← previous blocknext block →recent activity
Analyzing
Block #83,640,432
16 transactions · 15 stateful · 2026-06-25 16:56:03 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,640,432 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w17w28w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacb576ad…e0a1
0x34b655…2a6f
10 touches
10 conflicts
0x28a144f1…f8e9
0x34b655…2a6f
6 touches
3 conflicts
0x2cb897e4…21ea
0x34b655…2a6f
4 touches
1 conflict
0x329f2f7d…dcff
0x34b655…2a6f
4 touches
1 conflict
0x52a0e295…8847
0x34b655…2a6f
4 touches
1 conflict
0x6ceffbf3…4fe8
0x34b655…2a6f
4 touches
1 conflict
0x7e6c970a…65af
0x34b655…2a6f
4 touches
1 conflict
0x7fe97198…79ab
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 0xacb576ad50…3fe0a1
Audit this contract →
← previous block·next block →recent activity