← previous blocknext block →recent activity

Analyzing

Block #74,920,417

36 transactions · 27 stateful · 2026-05-16 07:15:34 UTC

Parallelism

72/100

Blocked

67%

Avg conflicts / tx

1.58

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,920,417  ·  36 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

0xe54a1f6f…18f2

0x34b655…2a6f

10 touches
10 conflicts

0xf9d49ef8…8c9f

0xd32edf…ff58

9 touches
10 conflicts

0x3e693216…fa0e

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x0711ec2d…d973

0x34b655…2a6f

6 touches
3 conflicts

0x707a047e…1dc1

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity