← previous blocknext block →recent activity

Analyzing

Block #74,631,836

16 transactions · 14 stateful · 2026-05-14 23:09:36 UTC

Parallelism

69/100

Blocked

43%

Avg conflicts / tx

0.81

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,631,836  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x00000000…0002

0xab3526…fa38

10 touches
10 conflicts

0xd49762c9…1359

0x34b655…2a6f

6 touches
3 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

6 touches
3 conflicts

0xc6417de0…2191

0xc8689a…ee79

6 touches
3 conflicts

0x0711ec2d…d973

0x34b655…2a6f

4 touches
1 conflict

0xa91c899f…6ee3

0x34b655…2a6f

4 touches
1 conflict

0x9be2b99a…a959

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

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: 0xab35264b…1cfa38

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity