← previous blocknext block →recent activity

Analyzing

Block #83,640,928

22 transactions · 16 stateful · 2026-06-25 16:59:21 UTC

Parallelism

68/100

Blocked

56%

Avg conflicts / tx

0.91

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #83,640,928  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xffb1ee54…7c2c

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xfc8b4565…aa86

0x34b655…2a6f

6 touches
3 conflicts

0x7e6c970a…65af

0x34b655…2a6f

4 touches
1 conflict

0x7ee6007b…fd68

0x34b655…2a6f

4 touches
1 conflict

0x7f8763d2…1510

0x34b655…2a6f

4 touches
1 conflict

0x7fe97198…79ab

0x34b655…2a6f

4 touches
1 conflict

0x93641233…06f5

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

15 conflicts on slot 0xffb1ee5457…d07c2c

← previous block·next block →recent activity