← previous blocknext block →recent activity
Analyzing
Block #83,642,833
11 transactions · 9 stateful · 2026-06-25 17:12:05 UTC
Parallelism
55/100
Blocked
44%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,642,833 · 11 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
1w02w13w28w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcde75077…ccee
0x34b655…2a6f
8 touches
6 conflicts
0x2592c29d…8a05
0x34b655…2a6f
6 touches
3 conflicts
0x13637b8e…57f0
0x34b655…2a6f
4 touches
1 conflict
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0x1175233a…64e7
0x34b655…2a6f
4 touches
1 conflict
0x7500c6c7…6b90
0x34b655…2a6f
4 touches
1 conflict
0x7e6c970a…65af
0x34b655…2a6f
4 touches
1 conflict
0x8651b4be…416c
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 0xcde75077a7…6dccee
Audit this contract →
← previous block·next block →recent activity