← previous blocknext block →recent activity
Analyzing
Block #83,616,459
17 transactions · 16 stateful · 2026-06-25 14:15:50 UTC
Parallelism
82/100
Blocked
25%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,616,459 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w05w18w09w110w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd7b809e…39b7
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xb02054c6…0967
0x34b655…2a6f
3 touches
1 conflict
0x651bc7dd…8d1d
0x34b655…2a6f
2 touches
0 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
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 0xcd7b809e3f…5239b7
Audit this contract →
← previous block·next block →recent activity