← previous blocknext block →recent activity

Analyzing

Block #74,436,528

24 transactions · 19 stateful · 2026-05-14 01:21:50 UTC

Parallelism

58/100

Blocked

53%

Avg conflicts / tx

1.79

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,436,528  ·  24 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

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

16 touches
28 conflicts

0xf3d10975…0d07

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

10 touches
10 conflicts

0x8cc18498…ce7e

0x34b655…2a6f

7 touches
6 conflicts

0x4d3e58e0…a2d7

0x34b655…2a6f

7 touches
6 conflicts

0xd40bddc1…773c

0x34b655…2a6f

6 touches
5 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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity