← previous blocknext block →recent activity

Analyzing

Block #74,510,161

14 transactions · 9 stateful · 2026-05-14 09:32:33 UTC

Parallelism

79/100

Blocked

22%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,510,161  ·  14 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

0x36b22589…ecb7

0x699abc…6a3b

6 touches
3 conflicts

0x37b154f1…c3fc

0x699abc…6a3b

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x335a161d…fe7f

0x000000…012a

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

2 touches
0 conflicts

0x085df2c1…305a

0x34b655…2a6f

2 touches
0 conflicts

0x22e0cc1d…ad04

0x34b655…2a6f

2 touches
0 conflicts

0x3f75fe28…5e14

0x34b655…2a6f

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: 0x699abc15…c86a3b

3 conflicts on slot 0x36b22589ea…13ecb7

← previous block·next block →recent activity