← previous blocknext block →recent activity

Analyzing

Block #83,210,110

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

Parallelism

88/100

Blocked

13%

Avg conflicts / tx

0.12

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #83,210,110  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x9a3068dd…18f0

0x34b655…2a6f

4 touches
1 conflict

0x9a3068dd…18f1

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x214e7853…074d

0x34b655…2a6f

4 touches
1 conflict

0xb96c408d…7113

0x34b655…2a6f

3 touches
1 conflict

0x4d04efa4…b3b5

0x40c49f…2af0

2 touches
0 conflicts

0x57a3cf74…16bb

0x40c49f…2af0

2 touches
0 conflicts

0xf4040809…c8fb

0x40c49f…2af0

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

1 conflict on slot 0x9a3068dd84…9918f0

← previous block·next block →recent activity