← previous blocknext block →recent activity

Analyzing

Block #83,863,996

16 transactions · 14 stateful · 2026-06-26 17:47:41 UTC

Parallelism

75/100

Blocked

64%

Avg conflicts / tx

0.81

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,863,996  ·  16 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

0xb99958f6…ccf0

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x2d5c395b…6b5a

0xa6afd3…d132

6 touches
3 conflicts

0x7c5260f4…bd96

0xa6afd3…d132

6 touches
3 conflicts

0x5a0123ab…54f3

0x34b655…2a6f

5 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

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 0xb99958f6c8…c6ccf0

← previous block·next block →recent activity