← previous blocknext block →recent activity

Analyzing

Block #74,515,289

45 transactions · 23 stateful · 2026-05-14 10:07:07 UTC

Parallelism

89/100

Blocked

52%

Avg conflicts / tx

0.56

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,515,289  ·  45 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x1c389468…6b0e

0x34b655…2a6f

8 touches
6 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xed90919b…bc43

0xd32edf…ff58

7 touches
6 conflicts

0xbc04d98e…a484

0x34b655…2a6f

6 touches
3 conflicts

0xe5e7089a…fb91

0x34b655…2a6f

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity