← previous blocknext block →recent activity

Analyzing

Block #73,686,485

14 transactions · 13 stateful · 2026-05-10 13:57:22 UTC

Parallelism

64/100

Blocked

31%

Avg conflicts / tx

0.86

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,686,485  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x0ac31945…2c72

0x065c9d…c394

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x00000000…000b

0x060728…d65c

2 touches
0 conflicts

0x0083181c…31bb

0x065c9d…c394

2 touches
0 conflicts

0x30c2a96f…bf31

0x065c9d…c394

2 touches
0 conflicts

0x529acb6a…fcc6

0x065c9d…c394

2 touches
0 conflicts

0x53480d7e…b076

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

10 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity