← previous blocknext block →recent activity

Analyzing

Block #74,359,694

19 transactions · 18 stateful · 2026-05-13 16:50:19 UTC

Parallelism

68/100

Blocked

61%

Avg conflicts / tx

1.42

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,359,694  ·  19 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xa472d565…9fe4

0x3bd359…433a

12 touches
15 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x11560115…bfc2

0x34b655…2a6f

8 touches
6 conflicts

0x1e9fccc4…5c21

0x34b655…2a6f

8 touches
6 conflicts

0x2965e2d6…5800

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

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: 0x3bd359c1…15433a

15 conflicts on slot 0xa472d565a0…ae9fe4

← previous block·next block →recent activity