← previous blocknext block →recent activity

Analyzing

Block #74,284,037

29 transactions · 21 stateful · 2026-05-13 08:27:06 UTC

Parallelism

79/100

Blocked

62%

Avg conflicts / tx

0.83

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,284,037  ·  29 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xb9d2cf20…a668

0x34b655…2a6f

8 touches
6 conflicts

0xf0270ed4…cd31

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0003

0x63e48b…53f2

6 touches
3 conflicts

0xd77e90ec…8c04

0x3bd359…433a

6 touches
3 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

6 touches
3 conflicts

0xf6cc7de8…0b4a

0x3bd359…433a

6 touches
3 conflicts

0x00000000…0000

0x63e48b…53f2

6 touches
3 conflicts

0x00000000…0004

0x63e48b…53f2

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

6 conflicts on slot 0xb9d2cf2005…28a668

← previous block·next block →recent activity