← previous blocknext block →recent activity

Analyzing

Block #74,637,889

18 transactions · 16 stateful · 2026-05-14 23:49:57 UTC

Parallelism

72/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,637,889  ·  18 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

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0x97b0b2ee…4666

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x8cea5724…5c29

0x34b655…2a6f

6 touches
3 conflicts

0xfa2527aa…9dd5

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xe5e7089a…fb91

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

6 conflicts on slot 0xf3981be56e…f02c47

← previous block·next block →recent activity