← previous blocknext block →recent activity

Analyzing

Block #74,455,826

18 transactions · 12 stateful · 2026-05-14 03:30:19 UTC

Parallelism

78/100

Blocked

33%

Avg conflicts / tx

0.39

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,455,826  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x1c389468…6b0e

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x9c2ed2a6…b501

0xd32edf…ff58

3 touches
1 conflict

0x00000000…0003

0x0594c7…a3be

2 touches
0 conflicts

0x00000000…0004

0x0594c7…a3be

2 touches
0 conflicts

0x00000000…0005

0x0594c7…a3be

2 touches
0 conflicts

0x7b59e08e…d4b0

0x0594c7…a3be

2 touches
0 conflicts

0xb504cd7e…5a81

0x0594c7…a3be

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

3 conflicts on slot 0x1c38946843…a16b0e

← previous block·next block →recent activity