← previous blocknext block →recent activity

Analyzing

Block #74,333,587

27 transactions · 22 stateful · 2026-05-13 13:56:44 UTC

Parallelism

63/100

Blocked

59%

Avg conflicts / tx

1.93

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,333,587  ·  27 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

20 touches
45 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xa92c8763…6d7f

0x34b655…2a6f

6 touches
3 conflicts

0x0f418e62…25fd

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x97b0b2ee…4666

0x34b655…2a6f

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

45 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity