← previous blocknext block →recent activity

Analyzing

Block #83,196,096

17 transactions · 14 stateful · 2026-06-23 15:29:02 UTC

Parallelism

82/100

Blocked

21%

Avg conflicts / tx

0.18

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #83,196,096  ·  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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xebbcae2a…16f8

0x34b655…2a6f

4 touches
1 conflict

0x0f3b22bf…e574

0x34b655…2a6f

4 touches
1 conflict

0x1ca68aab…5e4a

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x28ace1e6…cc7f

0x34b655…2a6f

4 touches
1 conflict

0x6f58168d…ea24

0x34b655…2a6f

4 touches
1 conflict

0x7506443a…4820

0x34b655…2a6f

4 touches
1 conflict

0x8b84e080…54ac

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

1 conflict on slot 0xebbcae2a12…8416f8

← previous block·next block →recent activity