← previous blocknext block →recent activity

Analyzing

Block #74,517,774

13 transactions · 9 stateful · 2026-05-14 10:23:51 UTC

Parallelism

77/100

Blocked

22%

Avg conflicts / tx

0.15

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,517,774  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xc108f63d…204f

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0efc210e…70ab

0x34b655…2a6f

4 touches
1 conflict

0x2aab0897…78f7

0x34b655…2a6f

4 touches
1 conflict

0x16c88549…bbe4

0x065c9d…c394

2 touches
0 conflicts

0x2250bf85…0c3b

0x065c9d…c394

2 touches
0 conflicts

0x5a0a316d…ba8d

0x065c9d…c394

2 touches
0 conflicts

0xcf44fd92…cd47

0x065c9d…c394

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

1 conflict on slot 0xc108f63d12…17204f

← previous block·next block →recent activity