← previous blocknext block →recent activity

Analyzing

Block #74,691,213

32 transactions · 23 stateful · 2026-05-15 05:45:30 UTC

Parallelism

72/100

Blocked

61%

Avg conflicts / tx

1.28

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,691,213  ·  32 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xb0e4f69d…34e1

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…0015

0x1b6862…e19c

14 touches
21 conflicts

0x00000000…0013

0x1b6862…e19c

14 touches
21 conflicts

0xb3cecb86…6df6

0xd32edf…ff58

13 touches
21 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0012

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0028

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…0018

0x1b6862…e19c

12 touches
15 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: 0x1b68626d…2de19c

21 conflicts on slot 0xb0e4f69d8e…c534e1

← previous block·next block →recent activity