← previous blocknext block →recent activity

Analyzing

Block #74,338,445

9 transactions · 9 stateful · 2026-05-13 14:29:05 UTC

Parallelism

78/100

Blocked

22%

Avg conflicts / tx

0.22

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,338,445  ·  9 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xecd87a39…d9c5

0x34b655…2a6f

4 touches
1 conflict

0xb6b74ae0…8d5e

0xea1b8e…c5ec

4 touches
1 conflict

0x00bac013…a28c

0xfd44b3…00d1

4 touches
1 conflict

0x3f1434d4…1ce1

0x11ed3b…2c96

2 touches
0 conflicts

0x00000000…006f

0x1efe02…37d6

2 touches
0 conflicts

0x5f47b4ad…567c

0x1efe02…37d6

2 touches
0 conflicts

0xa3c9a7af…d146

0x1efe02…37d6

2 touches
0 conflicts

0xf123b3fb…7bfb

0x1efe02…37d6

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 0xecd87a399c…10d9c5

← previous block·next block →recent activity