← previous blocknext block →recent activity

Analyzing

Block #73,610,069

16 transactions · 12 stateful · 2026-05-10 05:22:55 UTC

Parallelism

81/100

Blocked

17%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,610,069  ·  16 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

0xc3aacf13…6b3d

0x34b655…2a6f

6 touches
3 conflicts

0xb96e29a5…0419

0x34b655…2a6f

4 touches
1 conflict

0xac8e97a0…8426

0x34b655…2a6f

4 touches
1 conflict

0xff5c097d…680c

0x34b655…2a6f

4 touches
1 conflict

0x8db1e0f2…2fcf

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x7170c140…36bc

0x34b655…2a6f

4 touches
1 conflict

0xeb038f89…31d3

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

3 conflicts on slot 0xc3aacf13f1…5d6b3d

← previous block·next block →recent activity