← previous blocknext block →recent activity

Analyzing

Block #83,653,172

19 transactions · 17 stateful · 2026-06-25 18:21:07 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

0.68

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #83,653,172  ·  19 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

0xd2cdfa3f…f071

0x34b655…2a6f

6 touches
3 conflicts

0x51146258…3361

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

4 touches
1 conflict

0x756ad195…36a3

0x34b655…2a6f

4 touches
1 conflict

0x76bafa2e…d9a0

0x34b655…2a6f

4 touches
1 conflict

0x8d3f06db…98cb

0x34b655…2a6f

4 touches
1 conflict

0xd7fe05cd…207e

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