← previous blocknext block →recent activity

Analyzing

Block #74,450,153

16 transactions · 14 stateful · 2026-05-14 02:52:30 UTC

Parallelism

63/100

Blocked

43%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,450,153  ·  16 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x1728ed63…499c

0xea1b8e…c5ec

4 touches
1 conflict

0xb6b74ae0…8d5e

0xea1b8e…c5ec

4 touches
1 conflict

0x00bac013…a28c

0xfd44b3…00d1

4 touches
1 conflict

0x004346f0…34fe

0xd42a27…01c7

2 touches
0 conflicts

0x5e107c7d…4658

0xd42a27…01c7

2 touches
0 conflicts

0x5e107c7d…465a

0xd42a27…01c7

2 touches
0 conflicts

0x3115e80e…90f0

0xea1b8e…c5ec

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: 0xab35264b…1cfa38

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity