← previous blocknext block →recent activity

Analyzing

Block #74,510,348

18 transactions · 14 stateful · 2026-05-14 09:33:48 UTC

Parallelism

83/100

Blocked

36%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,510,348  ·  18 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

0x3f6168a9…d4f7

0xd32edf…ff58

5 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0x00000000…0004

0x465a0b…3980

4 touches
1 conflict

0x00000000…0005

0x465a0b…3980

4 touches
1 conflict

0x3b56d5f7…d11b

0x465a0b…3980

4 touches
1 conflict

0xb0f4dbcb…926a

0x754704…b603

4 touches
1 conflict

0xe069120c…952c

0x000000…012a

4 touches
1 conflict

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: 0xd32edf66…9fff58

3 conflicts on slot 0x3f6168a9e7…a7d4f7

← previous block·next block →recent activity