← previous blocknext block →recent activity

Analyzing

Block #83,967,110

23 transactions · 19 stateful · 2026-06-27 05:15:01 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

0.74

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,967,110  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xb3975d93…b4a2

0x34b655…2a6f

8 touches
6 conflicts

0x785889c9…0603

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xe99d8e68…a16e

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x66e47d07…baa6

0x34b655…2a6f

4 touches
1 conflict

0x793aa64d…b09c

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

6 conflicts on slot 0xb3975d9364…28b4a2

← previous block·next block →recent activity