← previous blocknext block →recent activity

Analyzing

Block #74,606,112

21 transactions · 17 stateful · 2026-05-14 20:18:07 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,606,112  ·  21 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

0x00000000…0002

0xab3526…fa38

12 touches
15 conflicts

0xf4b86ca4…cb7e

0xd32edf…ff58

7 touches
6 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x56a919c4…ab49

0x01bff4…1071

2 touches
0 conflicts

0x78eb0de5…1db2

0x01bff4…1071

2 touches
0 conflicts

0x40c0484d…8192

0x188d58…ea8e

2 touches
0 conflicts

0x40c0484d…8194

0x188d58…ea8e

2 touches
0 conflicts

0x703b861a…cbe3

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

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity