← previous blocknext block →recent activity

Analyzing

Block #73,609,711

16 transactions · 10 stateful · 2026-05-10 05:20:34 UTC

Parallelism

81/100

Blocked

20%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

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

0x9ea57326…329f

0x34b655…2a6f

6 touches
3 conflicts

0xa84d584e…d9c8

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x8240d70c…7c3b

0x34b655…2a6f

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

2 touches
0 conflicts

0x809e88f8…1f76

0x065c9d…c394

2 touches
0 conflicts

0xdb568be2…6213

0x065c9d…c394

2 touches
0 conflicts

0xf0ef078f…4528

0x065c9d…c394

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 0x9ea57326ca…60329f

← previous block·next block →recent activity