← previous blocknext block →recent activity

Analyzing

Block #73,328,492

16 transactions · 13 stateful · 2026-05-08 22:10:15 UTC

Parallelism

63/100

Blocked

38%

Avg conflicts / tx

0.69

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,328,492  ·  16 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

0x46cb45de…a567

0x188d58…ea8e

8 touches
6 conflicts

0x46cb45de…a566

0x188d58…ea8e

8 touches
6 conflicts

0xdeaaf11d…e96b

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x09beabbc…065c

0x188d58…ea8e

4 touches
1 conflict

0x09beabbc…065d

0x188d58…ea8e

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

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: 0x188d586d…f9ea8e

6 conflicts on slot 0x46cb45de01…66a567

← previous block·next block →recent activity