← previous blocknext block →recent activity

Analyzing

Block #74,240,735

23 transactions · 22 stateful · 2026-05-13 03:39:14 UTC

Parallelism

61/100

Blocked

45%

Avg conflicts / tx

1.7

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,240,735  ·  23 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0xf823e97f…2ee6

0x065c9d…c394

8 touches
6 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0003

0x139aab…382b

2 touches
0 conflicts

0x0520da1d…c88e

0x34b655…2a6f

2 touches
0 conflicts

0x17e2d2a0…359e

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

15 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity