← previous blocknext block →recent activity

Analyzing

Block #74,766,645

21 transactions · 19 stateful · 2026-05-15 14:09:34 UTC

Parallelism

62/100

Blocked

53%

Avg conflicts / tx

1.05

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,766,645  ·  21 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0xb89c7e78…0bee

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x6c1ea6f4…d950

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…002a

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

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

10 conflicts on slot 0x0000000000…000013

← previous block·next block →recent activity