← previous blocknext block →recent activity

Analyzing

Block #74,920,084

45 transactions · 32 stateful · 2026-05-16 07:13:20 UTC

Parallelism

80/100

Blocked

56%

Avg conflicts / tx

1.16

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,920,084  ·  45 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

0x60f7fbaf…bd58

0x34b655…2a6f

18 touches
36 conflicts

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

8 touches
6 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

8 touches
6 conflicts

0x9be2b99a…a959

0x34b655…2a6f

8 touches
6 conflicts

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0xdfa45ee2…45c6

0x34b655…2a6f

6 touches
3 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: 0x34b6552d…112a6f

36 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity