← previous blocknext block →recent activity

Analyzing

Block #74,518,393

22 transactions · 18 stateful · 2026-05-14 10:28:03 UTC

Parallelism

59/100

Blocked

44%

Avg conflicts / tx

1.64

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,518,393  ·  22 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xab3526…fa38

18 touches
36 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…001d

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002d

0x1b6862…e19c

2 touches
0 conflicts

0xba5743c7…21c4

0x1b6862…e19c

2 touches
0 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: 0xab35264b…1cfa38

36 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity