← previous blocknext block →recent activity

Analyzing

Block #74,763,043

34 transactions · 24 stateful · 2026-05-15 13:45:27 UTC

Parallelism

74/100

Blocked

58%

Avg conflicts / tx

1.21

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,763,043  ·  34 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

0x388e001a…7e04

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0xb9868b52…c77f

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x219e716d…27bf

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…002a

0x1b6862…e19c

6 touches
3 conflicts

0x17a7f697…dcb3

0x1b6862…e19c

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

10 conflicts on slot 0x388e001a16…e57e04

← previous block·next block →recent activity