← previous blocknext block →recent activity

Analyzing

Block #73,651,167

27 transactions · 20 stateful · 2026-05-10 09:59:02 UTC

Parallelism

78/100

Blocked

45%

Avg conflicts / tx

0.7

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,651,167  ·  27 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

0x15d039e7…4bb6

0x34b655…2a6f

8 touches
6 conflicts

0x85a88798…f85e

0x34b655…2a6f

8 touches
6 conflicts

0x1b5d2e60…99b5

0x34b655…2a6f

8 touches
6 conflicts

0x35b65947…44d1

0xc8689a…ee79

6 touches
3 conflicts

0xa8bd52b5…862e

0x34b655…2a6f

6 touches
3 conflicts

0xdceff93b…92ec

0x34b655…2a6f

6 touches
3 conflicts

0xdf671536…aa02

0x34b655…2a6f

6 touches
3 conflicts

0xef6b840d…1e8f

0x34b655…2a6f

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: 0x34b6552d…112a6f

6 conflicts on slot 0x15d039e716…294bb6

← previous block·next block →recent activity