← previous blocknext block →recent activity

Analyzing

Block #83,632,727

23 transactions · 19 stateful · 2026-06-25 16:04:34 UTC

Parallelism

74/100

Blocked

37%

Avg conflicts / tx

0.39

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,632,727  ·  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

0x022f72c3…07b6

0xc8689a…ee79

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xe99d8e68…a16e

0x34b655…2a6f

4 touches
1 conflict

0xf997c4c7…617d

0x34b655…2a6f

4 touches
1 conflict

0xffc2f21e…b393

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xaa7ee7…f0e4

4 touches
1 conflict

0x22e0cc1d…ad0d

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