← previous blocknext block →recent activity

Analyzing

Block #73,686,758

22 transactions · 13 stateful · 2026-05-10 13:59:12 UTC

Parallelism

86/100

Blocked

31%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,686,758  ·  22 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

0x3e733ae4…4598

0x34b655…2a6f

6 touches
3 conflicts

0xaa8a1c54…ead3

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xece5f354…cb94

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x65e27d5f…f96d

0xd32edf…ff58

3 touches
1 conflict

0x2e4d015b…d927

0x065c9d…c394

2 touches
0 conflicts

0x40e58b81…7910

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 0x3e733ae4c3…f54598

← previous block·next block →recent activity