← previous blocknext block →recent activity

Analyzing

Block #74,517,666

15 transactions · 11 stateful · 2026-05-14 10:23:08 UTC

Parallelism

80/100

Blocked

18%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,517,666  ·  15 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

4 touches
1 conflict

0xc3aacf13…6b3d

0x34b655…2a6f

4 touches
1 conflict

0xeebd31ac…0794

0x34b655…2a6f

4 touches
1 conflict

0x421f9453…324a

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0x75c5222a…8291

0x065c9d…c394

2 touches
0 conflicts

0x7af666c6…6ad2

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity