← previous blocknext block →recent activity

Analyzing

Block #73,170,740

18 transactions · 15 stateful · 2026-05-08 04:40:20 UTC

Parallelism

83/100

Blocked

40%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,170,740  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x4e5ebbf7…ae70

0xc8689a…ee79

6 touches
3 conflicts

0xbc7a7347…fc9a

0x34b655…2a6f

6 touches
3 conflicts

0xd984a5e4…5cfc

0x34b655…2a6f

6 touches
3 conflicts

0xef17b8cd…9511

0x34b655…2a6f

6 touches
3 conflicts

0x1a4b4152…0a08

0x6ca43f…c331

6 touches
3 conflicts

0x3e4b8d9f…b8a7

0x6ca43f…c331

6 touches
3 conflicts

0xc5564f8e…f4bf

0x6ca43f…c331

6 touches
3 conflicts

0xf0f673fd…37a7

0x6ca43f…c331

6 touches
3 conflicts

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: 0xc8689a47…62ee79

3 conflicts on slot 0x4e5ebbf7fb…3fae70

← previous block·next block →recent activity