← previous blocknext block →recent activity

Analyzing

Block #74,813,628

29 transactions · 26 stateful · 2026-05-15 19:24:01 UTC

Parallelism

72/100

Blocked

69%

Avg conflicts / tx

1.62

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,813,628  ·  29 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x8c49c85c…ee96

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x41755291…977f

0x065c9d…c394

8 touches
6 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0x47b807a2…3307

0x065c9d…c394

8 touches
6 conflicts

0x6fd9ae7c…e980

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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 0x8c49c85c3e…afee96

← previous block·next block →recent activity