← previous blocknext block →recent activity

Analyzing

Block #83,630,026

21 transactions · 16 stateful · 2026-06-25 15:46:31 UTC

Parallelism

81/100

Blocked

31%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,630,026  ·  21 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

0xd7add284…8d28

0x34b655…2a6f

8 touches
6 conflicts

0x31aa2853…8dbb

0xc8689a…ee79

4 touches
1 conflict

0x8a5efe9a…fa31

0x34b655…2a6f

4 touches
1 conflict

0xacc69dfd…193c

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64dc

0x34b655…2a6f

4 touches
1 conflict

0xd79c9727…1233

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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 0xd7add284d9…568d28

← previous block·next block →recent activity