← previous blocknext block →recent activity

Analyzing

Block #74,920,557

19 transactions · 17 stateful · 2026-05-16 07:16:30 UTC

Parallelism

74/100

Blocked

47%

Avg conflicts / tx

0.89

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,920,557  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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…0015

0x1b6862…e19c

8 touches
6 conflicts

0xf8480e2a…dff3

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x87a18d4e…01ce

0xd32edf…ff58

7 touches
6 conflicts

0x765c236f…ff45

0x2a68ba…90c5

6 touches
3 conflicts

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

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

6 conflicts on slot 0x0000000000…000015

← previous block·next block →recent activity