← previous blocknext block →recent activity

Analyzing

Block #83,639,939

17 transactions · 16 stateful · 2026-06-25 16:52:46 UTC

Parallelism

76/100

Blocked

50%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,639,939  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0xffb1ee54…7c2c

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x2f4d415d…5f95

0x34b655…2a6f

4 touches
1 conflict

0x329f2f7d…dcff

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x6215b1a0…cae2

0x34b655…2a6f

4 touches
1 conflict

0x7e6c970a…65af

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

3 conflicts on slot 0xe99d8e683a…2ea16e

← previous block·next block →recent activity