← previous blocknext block →recent activity

Analyzing

Block #74,025,978

18 transactions · 12 stateful · 2026-05-12 03:50:43 UTC

Parallelism

61/100

Blocked

58%

Avg conflicts / tx

0.72

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,025,978  ·  18 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

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x2a2896a0…2a0a

0x34b655…2a6f

4 touches
1 conflict

0x2fad73a1…ae09

0x34b655…2a6f

4 touches
1 conflict

0xb110d1eb…61bc

0x34b655…2a6f

4 touches
1 conflict

0xb6ed511f…6b68

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xfe39a1f7…8eb0

0x34b655…2a6f

4 touches
1 conflict

0x318ac0bb…6b9c

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

10 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity