← previous blocknext block →recent activity

Analyzing

Block #74,247,586

18 transactions · 16 stateful · 2026-05-13 04:24:46 UTC

Parallelism

67/100

Blocked

63%

Avg conflicts / tx

1.39

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,247,586  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x98c09d43…028f

0xd32edf…ff58

11 touches
15 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

8 touches
6 conflicts

0x2b9c6652…d14e

0x754704…b603

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x3bd55803…5d4f

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

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

15 conflicts on slot 0x98c09d434f…8c028f

← previous block·next block →recent activity