← previous blocknext block →recent activity

Analyzing

Block #74,597,493

26 transactions · 13 stateful · 2026-05-14 19:20:06 UTC

Parallelism

85/100

Blocked

46%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,597,493  ·  26 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xf9470055…bbf8

0x34b655…2a6f

6 touches
3 conflicts

0x10814d14…cdda

0x34b655…2a6f

4 touches
1 conflict

0x23a320fb…cbd7

0x34b655…2a6f

4 touches
1 conflict

0x51087f5a…61f7

0x34b655…2a6f

4 touches
1 conflict

0x5e803aa6…bbd4

0x34b655…2a6f

4 touches
1 conflict

0x6ced6109…8d91

0x34b655…2a6f

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: 0x34b6552d…112a6f

3 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity