← previous blocknext block →recent activity

Analyzing

Block #74,607,318

22 transactions · 19 stateful · 2026-05-14 20:26:12 UTC

Parallelism

59/100

Blocked

47%

Avg conflicts / tx

1.23

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,607,318  ·  22 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

8 touches
6 conflicts

0x42446806…33dd

0x34b655…2a6f

4 touches
1 conflict

0x4ec9114f…44c2

0x34b655…2a6f

4 touches
1 conflict

0x55b6a001…1e7a

0x34b655…2a6f

4 touches
1 conflict

0x57de3828…3fbb

0x34b655…2a6f

4 touches
1 conflict

0x59ef13ba…2741

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity