← previous blocknext block →recent activity

Analyzing

Block #74,643,963

20 transactions · 16 stateful · 2026-05-15 00:30:24 UTC

Parallelism

70/100

Blocked

31%

Avg conflicts / tx

0.75

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,643,963  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xc77936b6…92c7

0xd32edf…ff58

11 touches
15 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x12309510…0ac2

0x000000…012a

2 touches
0 conflicts

0xf6802cf0…344f

0x000000…012a

2 touches
0 conflicts

0x56a919c4…ab49

0x01bff4…1071

2 touches
0 conflicts

0x78eb0de5…1db2

0x01bff4…1071

2 touches
0 conflicts

0x2cfe5229…f285

0x188d58…ea8e

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: 0xd32edf66…9fff58

15 conflicts on slot 0xc77936b691…3092c7

← previous block·next block →recent activity