← previous blocknext block →recent activity

Analyzing

Block #74,218,498

27 transactions · 20 stateful · 2026-05-13 01:11:25 UTC

Parallelism

70/100

Blocked

45%

Avg conflicts / tx

0.81

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,218,498  ·  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

0x877173fb…7f5f

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x8b41ec8f…c2da

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002f

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xcf3283ba…c9fa

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0012

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

15 conflicts on slot 0x877173fb93…1c7f5f

← previous block·next block →recent activity