← previous blocknext block →recent activity

Analyzing

Block #74,920,561

27 transactions · 21 stateful · 2026-05-16 07:16:32 UTC

Parallelism

74/100

Blocked

52%

Avg conflicts / tx

1.3

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,920,561  ·  27 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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xbf97274f…79d9

0xd32edf…ff58

9 touches
10 conflicts

0x50f2372e…df46

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xb9868b52…c77f

0x34b655…2a6f

6 touches
3 conflicts

0x19fe117b…bf8a

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: Perpl

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity