← previous blocknext block →recent activity

Analyzing

Block #74,425,126

34 transactions · 21 stateful · 2026-05-14 00:05:54 UTC

Parallelism

62/100

Blocked

67%

Avg conflicts / tx

2.38

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #74,425,126  ·  34 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0xb359818a…64d1

0xd32edf…ff58

25 touches
78 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x33018431…8f5c

0x188d58…ea8e

4 touches
1 conflict

0x33018431…8f5d

0x188d58…ea8e

4 touches
1 conflict

0x4dd1db39…a994

0x188d58…ea8e

4 touches
1 conflict

0x4dd1db39…a995

0x188d58…ea8e

4 touches
1 conflict

0x4dd1db39…a997

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0012

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

78 conflicts on slot 0xb359818a2b…8864d1

← previous block·next block →recent activity