← previous blocknext block →recent activity

Analyzing

Block #73,609,194

10 transactions · 10 stateful · 2026-05-10 05:17:07 UTC

Parallelism

70/100

Blocked

20%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,609,194  ·  10 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

0xb91a6f59…722c

0x34b655…2a6f

4 touches
1 conflict

0x9ea57326…329f

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x2877f440…c2c8

0x34b655…2a6f

2 touches
0 conflicts

0x9c3992e7…5a90

0x34b655…2a6f

2 touches
0 conflicts

0xb6404137…3951

0x34b655…2a6f

2 touches
0 conflicts

0xb82bffbd…c6de

0x34b655…2a6f

2 touches
0 conflicts

0xc824469a…641c

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 0xb91a6f59b9…c8722c

← previous block·next block →recent activity