← previous blocknext block →recent activity

Analyzing

Block #74,356,557

17 transactions · 16 stateful · 2026-05-13 16:29:30 UTC

Parallelism

59/100

Blocked

44%

Avg conflicts / tx

1.18

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,356,557  ·  17 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

0x5cfec795…7c0e

0x34b655…2a6f

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

10 touches
10 conflicts

0xafd59af5…5257

0xc8689a…ee79

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x6f2e60dc…e661

0x34b655…2a6f

8 touches
6 conflicts

0xbfca3cd0…5023

0x34b655…2a6f

8 touches
6 conflicts

0xc5940545…27fe

0x34b655…2a6f

6 touches
3 conflicts

0x3541b230…4a78

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

15 conflicts on slot 0x5cfec7957f…867c0e

← previous block·next block →recent activity