← previous blocknext block →recent activity

Analyzing

Block #74,456,755

36 transactions · 29 stateful · 2026-05-14 03:36:31 UTC

Parallelism

75/100

Blocked

66%

Avg conflicts / tx

1.72

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,456,755  ·  36 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

18 touches
36 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0x374426df…f445

0xc8689a…ee79

6 touches
3 conflicts

0x7cee1be1…e770

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe9976b58…82b8

0x34b655…2a6f

6 touches
3 conflicts

0x0f418e62…25fd

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

36 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity