← previous blocknext block →recent activity

Analyzing

Block #74,954,259

16 transactions · 14 stateful · 2026-05-16 11:02:01 UTC

Parallelism

63/100

Blocked

36%

Avg conflicts / tx

0.56

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,954,259  ·  16 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

0x8a35acfb…d1a6

0x8d66a4…3095

7 touches
6 conflicts

0xd49762c9…1359

0x34b655…2a6f

6 touches
3 conflicts

0x17cd1479…00bb

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1a0

0x8d66a4…3095

6 touches
3 conflicts

0xe54a1f6f…18f2

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x1550e185…0b12

0x34b655…2a6f

6 touches
3 conflicts

0xfff38d9f…7063

0x8d66a4…3095

5 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: 0x8d66a43f…113095

6 conflicts on slot 0x8a35acfbc1…6bd1a6

← previous block·next block →recent activity