← previous blocknext block →recent activity

Analyzing

Block #73,816,937

11 transactions · 9 stateful · 2026-05-11 04:36:19 UTC

Parallelism

45/100

Blocked

56%

Avg conflicts / tx

1.09

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,816,937  ·  11 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0x0375b9c4…455d

0x2ab50b…5c41

2 touches
0 conflicts

0x0849cefc…6a65

0x2ab50b…5c41

2 touches
0 conflicts

0x0a779f88…6e18

0x2ab50b…5c41

2 touches
0 conflicts

0x15a8b5e6…0296

0x2ab50b…5c41

2 touches
0 conflicts

0x1a357670…7396

0x2ab50b…5c41

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity