← previous blocknext block →recent activity

Analyzing

Block #72,975,895

18 transactions · 15 stateful · 2026-05-07 07:04:04 UTC

Parallelism

83/100

Blocked

33%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,975,895  ·  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

0xdaca243a…f9de

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x76e80753…03d6

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xa1e57f6e…95c3

0xd32edf…ff58

3 touches
1 conflict

0x5855c175…a893

0x065c9d…c394

2 touches
0 conflicts

0x8e4b04b8…7ff9

0x065c9d…c394

2 touches
0 conflicts

0xcbb58d52…98c6

0x065c9d…c394

2 touches
0 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

3 conflicts on slot 0xdaca243a5e…09f9de

← previous block·next block →recent activity