← previous blocknext block →recent activity

Analyzing

Block #83,639,048

19 transactions · 18 stateful · 2026-06-25 16:46:48 UTC

Parallelism

79/100

Blocked

44%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #83,639,048  ·  19 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

0xe2ebed66…8be2

0x34b655…2a6f

6 touches
3 conflicts

0xec0e0220…cb90

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x1175233a…64e7

0x34b655…2a6f

6 touches
3 conflicts

0xffb1ee54…7c2c

0x34b655…2a6f

6 touches
3 conflicts

0x164199ad…aa12

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xb43f291a…65b4

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 0xe2ebed6614…578be2

← previous block·next block →recent activity