← previous blocknext block →recent activity

Analyzing

Block #74,538,710

14 transactions · 12 stateful · 2026-05-14 12:45:02 UTC

Parallelism

86/100

Blocked

8%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,538,710  ·  14 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

0xb2e41bf7…4f55

0x699abc…6a3b

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xc8cdc8e3…2b46

0x699abc…6a3b

4 touches
1 conflict

0x335a161d…fe7f

0x000000…012a

4 touches
1 conflict

0x72a152dd…9f81

0x16f70c…c3dd

2 touches
0 conflicts

0xdd5dd18a…fdb2

0x3e4f2b…ba84

2 touches
0 conflicts

0x1a7b2836…f522

0x58e158…3d57

2 touches
0 conflicts

0x3dea5c3d…5fb8

0x58e158…3d57

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

1 conflict on slot 0xb2e41bf7c0…b64f55

← previous block·next block →recent activity