← previous blocknext block →recent activity

Analyzing

Block #83,625,303

20 transactions · 16 stateful · 2026-06-25 15:14:56 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

0.55

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,625,303  ·  20 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

8 touches
6 conflicts

0x00000000…0002

0xaa7ee7…f0e4

4 touches
1 conflict

0x76ed8777…1e5f

0x34b655…2a6f

4 touches
1 conflict

0x875955b6…7653

0x34b655…2a6f

4 touches
1 conflict

0x97cea457…9249

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd06d821c…e5d0

0x34b655…2a6f

4 touches
1 conflict

0xd848d054…2117

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

← previous block·next block →recent activity