← previous blocknext block →recent activity

Analyzing

Block #74,462,741

9 transactions · 9 stateful · 2026-05-14 04:16:22 UTC

Parallelism

78/100

Blocked

11%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,462,741  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xa486f342…64d5

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0x28c180e1…f1e2

0x34b655…2a6f

4 touches
1 conflict

0x7cee1be1…e770

0x34b655…2a6f

4 touches
1 conflict

0x1c389468…6b0e

0x34b655…2a6f

2 touches
0 conflicts

0x269c9f42…7a5d

0x34b655…2a6f

2 touches
0 conflicts

0x55d9e516…1ff1

0x34b655…2a6f

2 touches
0 conflicts

0x8d13ecc1…980f

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

1 conflict on slot 0xa486f34281…4664d5

← previous block·next block →recent activity