← previous blocknext block →recent activity

Analyzing

Block #74,742,605

44 transactions · 32 stateful · 2026-05-15 11:28:35 UTC

Parallelism

80/100

Blocked

63%

Avg conflicts / tx

0.95

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,742,605  ·  44 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

0xd61dad7d…2e84

0xd32edf…ff58

13 touches
21 conflicts

0xf3d7a307…4d63

0x065c9d…c394

8 touches
6 conflicts

0x801a6e57…d85c

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0029

0x1b6862…e19c

4 touches
1 conflict

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: 0xd32edf66…9fff58

21 conflicts on slot 0xd61dad7da2…542e84

← previous block·next block →recent activity