← previous blocknext block →recent activity

Analyzing

Block #74,335,724

13 transactions · 12 stateful · 2026-05-13 14:10:56 UTC

Parallelism

23/100

Blocked

75%

Avg conflicts / tx

3.46

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,335,724  ·  13 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xa7283d…0ace

20 touches
45 conflicts

0x8fa7a69c…8fd7

0xf9bede…7777

20 touches
45 conflicts

0x29801da0…be36

0xa7283d…0ace

20 touches
45 conflicts

0x29801da0…be37

0xa7283d…0ace

20 touches
45 conflicts

0x29801da0…be38

0xa7283d…0ace

20 touches
45 conflicts

0x29801da0…be39

0xa7283d…0ace

20 touches
45 conflicts

0x536e2740…61ac

0x3bd359…433a

20 touches
45 conflicts

0xa472d565…9fe4

0x3bd359…433a

20 touches
45 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: 0xa7283d07…f90ace

45 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity