← previous blocknext block →recent activity

Analyzing

Block #74,459,173

43 transactions · 27 stateful · 2026-05-14 03:52:36 UTC

Parallelism

81/100

Blocked

44%

Avg conflicts / tx

0.93

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,459,173  ·  43 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

0x43e28e94…0d31

0xd32edf…ff58

15 touches
28 conflicts

0x56a919c4…ab49

0xee8c0e…1242

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001c

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002c

0x1b6862…e19c

6 touches
3 conflicts

0xd381d0e5…7435

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

28 conflicts on slot 0x43e28e9448…c60d31

← previous block·next block →recent activity