← previous blocknext block →recent activity

Analyzing

Block #74,762,777

31 transactions · 27 stateful · 2026-05-15 13:43:39 UTC

Parallelism

74/100

Blocked

59%

Avg conflicts / tx

1.55

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,762,777  ·  31 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

16 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xfd4556a5…bf8b

0xd32edf…ff58

7 touches
6 conflicts

0xa92c8763…6d7f

0x34b655…2a6f

6 touches
3 conflicts

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0xab2a87f1…eafd

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x1e6db1fe…8d8b

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

28 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity