← previous blocknext block →recent activity

Analyzing

Block #74,309,359

14 transactions · 12 stateful · 2026-05-13 11:15:37 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,309,359  ·  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

0x84aef2aa…979f

0x34b655…2a6f

4 touches
1 conflict

0xbb1747e2…f78b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xdd70bea3…1ffe

0x3bd359…433a

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x00000000…006f

0x1efe02…37d6

2 touches
0 conflicts

0x025e49d9…12f7

0x1efe02…37d6

2 touches
0 conflicts

0x16fb7d78…f2c1

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 0x84aef2aa0a…df979f

← previous block·next block →recent activity