← previous blocknext block →recent activity

Analyzing

Block #74,766,913

27 transactions · 20 stateful · 2026-05-15 14:11:22 UTC

Parallelism

63/100

Blocked

60%

Avg conflicts / tx

1.37

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,766,913  ·  27 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x0d06899c…e988

0xd32edf…ff58

13 touches
21 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

12 touches
15 conflicts

0xbc815594…7278

0x065c9d…c394

12 touches
15 conflicts

0xa1087a5c…66c4

0x754704…b603

12 touches
15 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0xba5743c7…21c1

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

21 conflicts on slot 0x0d06899c50…2ee988

← previous block·next block →recent activity