← previous blocknext block →recent activity

Analyzing

Block #73,748,801

13 transactions · 11 stateful · 2026-05-10 20:57:49 UTC

Parallelism

77/100

Blocked

27%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,748,801  ·  13 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

0x53aedbbb…a150

0x34b655…2a6f

4 touches
1 conflict

0x8aa24fd1…2aa5

0x34b655…2a6f

4 touches
1 conflict

0x7f81fb82…633e

0x065c9d…c394

4 touches
1 conflict

0x15d039e7…4bb6

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x45b9e08c…a11b

0x34b655…2a6f

2 touches
0 conflicts

0x57de3828…3fbb

0x34b655…2a6f

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

1 conflict on slot 0x53aedbbbf7…bea150

← previous block·next block →recent activity