← previous blocknext block →recent activity

Analyzing

Block #74,407,104

29 transactions · 22 stateful · 2026-05-13 22:05:58 UTC

Parallelism

83/100

Blocked

45%

Avg conflicts / tx

0.59

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,407,104  ·  29 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0x537e2e5b…c3ab

0x34b655…2a6f

6 touches
3 conflicts

0x00bac013…a28c

0xfd44b3…00d1

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0xab981df1…2941

0x34b655…2a6f

4 touches
1 conflict

0xaf498679…7732

0x34b655…2a6f

4 touches
1 conflict

0xecd87a39…d9c5

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity