← previous blocknext block →recent activity

Analyzing

Block #73,261,493

14 transactions · 13 stateful · 2026-05-08 14:44:17 UTC

Parallelism

79/100

Blocked

15%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,261,493  ·  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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x0b390c61…dc07

0x065c9d…c394

4 touches
1 conflict

0x6eb27867…b633

0x188d58…ea8e

2 touches
0 conflicts

0x7887eb6e…75f5

0x188d58…ea8e

2 touches
0 conflicts

0xab2f6eed…254d

0x188d58…ea8e

2 touches
0 conflicts

0x4d970796…1a44

0x34b655…2a6f

2 touches
0 conflicts

0x51087f5a…61f7

0x34b655…2a6f

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