← previous blocknext block →recent activity

Analyzing

Block #74,353,739

30 transactions · 23 stateful · 2026-05-13 16:10:42 UTC

Parallelism

77/100

Blocked

52%

Avg conflicts / tx

0.97

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,353,739  ·  30 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

12 touches
15 conflicts

0x9d1bb389…c7d9

0x8d66a4…3095

8 touches
6 conflicts

0x0335ae80…8414

0x8d66a4…3095

8 touches
6 conflicts

0x17cd1479…00bb

0x8d66a4…3095

8 touches
6 conflicts

0x8a35acfb…d1a8

0x8d66a4…3095

8 touches
6 conflicts

0x8a35acfb…d1a9

0x8d66a4…3095

7 touches
6 conflicts

0xa54d4519…267f

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

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 0x60f7fbaf90…97bd58

← previous block·next block →recent activity