← previous blocknext block →recent activity

Analyzing

Block #74,958,938

27 transactions · 20 stateful · 2026-05-16 11:33:32 UTC

Parallelism

70/100

Blocked

45%

Avg conflicts / tx

1.11

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,958,938  ·  27 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x3e49348b…9445

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xea02471d…1542

0x34b655…2a6f

14 touches
21 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

10 touches
10 conflicts

0xf3d10975…0d07

0x34b655…2a6f

10 touches
10 conflicts

0xae6a4c09…c78a

0x34b655…2a6f

9 touches
10 conflicts

0x8fbde2b3…9b8f

0x34b655…2a6f

8 touches
6 conflicts

0x41d3bfa5…523e

0x34b655…2a6f

6 touches
4 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: Perpl

21 conflicts on slot 0x3e49348b38…839445

← previous block·next block →recent activity