← previous blocknext block →recent activity

Analyzing

Block #74,786,872

7 transactions · 5 stateful · 2026-05-15 16:24:50 UTC

Parallelism

71/100

Blocked

20%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,786,872  ·  7 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xc2fc05e8…5250

0xea1b8e…c5ec

4 touches
1 conflict

0xb6b74ae0…8d5e

0xea1b8e…c5ec

4 touches
1 conflict

0xc2fc05e8…5252

0xea1b8e…c5ec

4 touches
1 conflict

0xbc33a929…8b24

0xea1b8e…c5ec

4 touches
1 conflict

0x455b104f…3960

0xea1b8e…c5ec

4 touches
1 conflict

0x1728ed63…499c

0xea1b8e…c5ec

2 touches
0 conflicts

0xc2fc05e8…524e

0xea1b8e…c5ec

2 touches
0 conflicts

0xc2fc05e8…5251

0xea1b8e…c5ec

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: 0xea1b8e4a…8fc5ec

1 conflict on slot 0xc2fc05e867…605250

← previous block·next block →recent activity