← previous blocknext block →recent activity

Analyzing

Block #73,971,336

14 transactions · 12 stateful · 2026-05-11 21:44:33 UTC

Parallelism

79/100

Blocked

17%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,971,336  ·  14 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

0xac8e97a0…8426

0x34b655…2a6f

6 touches
3 conflicts

0x908d4442…2c4b

0x34b655…2a6f

4 touches
1 conflict

0x8db1e0f2…2fcf

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x120182c5…1647

0x065c9d…c394

2 touches
0 conflicts

0x3c16c902…2961

0x065c9d…c394

2 touches
0 conflicts

0x71dfffb9…1c1b

0x065c9d…c394

2 touches
0 conflicts

0x9646beaf…8bc3

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 0xac8e97a09a…ea8426

← previous block·next block →recent activity