← previous blocknext block →recent activity

Analyzing

Block #74,489,830

16 transactions · 13 stateful · 2026-05-14 07:16:33 UTC

Parallelism

44/100

Blocked

62%

Avg conflicts / tx

1.81

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,489,830  ·  16 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xc6417de0…2191

0xc8689a…ee79

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x908d4442…2c4b

0x34b655…2a6f

12 touches
15 conflicts

0x99f080dc…58c1

0x34b655…2a6f

12 touches
15 conflicts

0xac8e97a0…8426

0x34b655…2a6f

12 touches
15 conflicts

0xba85143e…a3e5

0x34b655…2a6f

12 touches
15 conflicts

0xc3aacf13…6b3d

0x34b655…2a6f

12 touches
15 conflicts

0xd1c4b51a…7e3e

0x34b655…2a6f

12 touches
15 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: 0xc8689a47…62ee79

15 conflicts on slot 0xc6417de023…802191

← previous block·next block →recent activity