← previous blocknext block →recent activity

Analyzing

Block #74,775,022

26 transactions · 21 stateful · 2026-05-15 15:05:41 UTC

Parallelism

69/100

Blocked

52%

Avg conflicts / tx

1.54

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,775,022  ·  26 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

0x00000000…0001

0x7d0364…a52b

16 touches
28 conflicts

0x131ec7f4…baaf

0xaca864…7777

16 touches
28 conflicts

0xa472d565…9fe4

0x3bd359…433a

16 touches
28 conflicts

0xaadf42dc…f433

0x3bd359…433a

16 touches
28 conflicts

0x00000000…0000

0x7d0364…a52b

16 touches
28 conflicts

0x44ad89ba…cf83

0xaca864…7777

16 touches
28 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

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: 0x7d036474…8da52b

28 conflicts on slot 0x0000000000…000001

← previous block·next block →recent activity