← previous blocknext block →recent activity

Analyzing

Block #74,428,659

28 transactions · 21 stateful · 2026-05-14 00:29:23 UTC

Parallelism

61/100

Blocked

67%

Avg conflicts / tx

2.29

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,428,659  ·  28 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x93d2a528…2d51

0xd32edf…ff58

21 touches
55 conflicts

0x00000000…0001

0x116e7d…d8f1

10 touches
10 conflicts

0x00000000…0003

0x116e7d…d8f1

10 touches
10 conflicts

0xb7143610…adc4

0x3bd359…433a

10 touches
10 conflicts

0x00000000…0000

0x116e7d…d8f1

10 touches
10 conflicts

0x692a4122…76b8

0x350035…7777

10 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xba5743c7…21c2

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

55 conflicts on slot 0x93d2a528b2…d62d51

← previous block·next block →recent activity