← previous blocknext block →recent activity

Analyzing

Block #73,297,359

14 transactions · 13 stateful · 2026-05-08 18:42:59 UTC

Parallelism

64/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,297,359  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x98e3c7a7…c949

0xd32edf…ff58

5 touches
3 conflicts

0x4423a307…9f46

0x1b6862…e19c

4 touches
1 conflict

0xbdff944d…447e

0x2a68ba…90c5

4 touches
1 conflict

0x8f375dda…1b11

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0x2c2ae2ac…1742

0x065c9d…c394

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

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: 0xd32edf66…9fff58

3 conflicts on slot 0x98e3c7a75d…35c949

← previous block·next block →recent activity