← previous blocknext block →recent activity

Analyzing

Block #83,197,681

23 transactions · 19 stateful · 2026-06-23 15:39:39 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.61

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,197,681  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xac0f2a19…d2e0

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x8b305a3b…1c35

0x34b655…2a6f

6 touches
3 conflicts

0xd5dbfacf…c5ec

0x34b655…2a6f

6 touches
3 conflicts

0x4e638546…0894

0x34b655…2a6f

4 touches
1 conflict

0x57be321f…fecc

0x34b655…2a6f

4 touches
1 conflict

0x5f447436…f3d4

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity