← previous blocknext block →recent activity

Analyzing

Block #74,319,440

32 transactions · 25 stateful · 2026-05-13 12:22:43 UTC

Parallelism

78/100

Blocked

60%

Avg conflicts / tx

1.34

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,319,440  ·  32 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x56a919c4…ab49

0xee8c0e…1242

12 touches
15 conflicts

0x4fd6a315…21d3

0xd32edf…ff58

11 touches
15 conflicts

0x8a0d91a0…2b15

0x34b655…2a6f

8 touches
6 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0019

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0029

0x1b6862…e19c

8 touches
6 conflicts

0x78694995…f668

0x1b6862…e19c

8 touches
6 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: 0xee8c0e9f…481242

15 conflicts on slot 0x56a919c43e…27ab49

← previous block·next block →recent activity