← previous blocknext block →recent activity

Analyzing

Block #74,473,250

18 transactions · 14 stateful · 2026-05-14 05:26:09 UTC

Parallelism

72/100

Blocked

43%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,473,250  ·  18 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

0x11cb770d…a0a3

0x34b655…2a6f

8 touches
6 conflicts

0xadac4a86…c2bc

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x33018431…8f5c

0x188d58…ea8e

4 touches
1 conflict

0x33018431…8f5e

0x188d58…ea8e

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

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

6 conflicts on slot 0x11cb770d51…54a0a3

← previous block·next block →recent activity