← previous blocknext block →recent activity

Analyzing

Block #74,736,224

27 transactions · 24 stateful · 2026-05-15 10:46:03 UTC

Parallelism

70/100

Blocked

46%

Avg conflicts / tx

1.04

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,736,224  ·  27 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

0xf6d3baf0…87a2

0xd32edf…ff58

11 touches
15 conflicts

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21c0

0x1b6862…e19c

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x12309510…0ac2

0x000000…012a

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 0xf6d3baf0f4…6f87a2

← previous block·next block →recent activity