← previous blocknext block →recent activity

Analyzing

Block #74,646,904

31 transactions · 28 stateful · 2026-05-15 00:49:59 UTC

Parallelism

77/100

Blocked

61%

Avg conflicts / tx

1.61

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,646,904  ·  31 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xadac4a86…c2bc

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x0b6d25a1…2e3b

0x34b655…2a6f

10 touches
10 conflicts

0x17606ba6…1b6e

0x754704…b603

10 touches
10 conflicts

0xa9b79f6e…69c0

0xd32edf…ff58

9 touches
10 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x6af306bb…2e81

0x3bd359…433a

8 touches
6 conflicts

0xf91b744e…9117

0x754704…b603

8 touches
6 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: 0x34b6552d…112a6f

21 conflicts on slot 0xadac4a860c…a3c2bc

← previous block·next block →recent activity