← previous blocknext block →recent activity

Analyzing

Block #73,476,201

11 transactions · 9 stateful · 2026-05-09 14:33:00 UTC

Parallelism

73/100

Blocked

33%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,476,201  ·  11 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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x50ed20f4…f48b

0xd32edf…ff58

3 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x670e1ac0…17b4

0x0555e3…2b9c

2 touches
0 conflicts

0x846f2172…fd54

0x0555e3…2b9c

2 touches
0 conflicts

0x05037959…436b

0x065c9d…c394

2 touches
0 conflicts

0x6f08361d…bda6

0x065c9d…c394

2 touches
0 conflicts

0xb2408af5…01c8

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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity