← previous blocknext block →recent activity

Analyzing

Block #74,606,102

15 transactions · 14 stateful · 2026-05-14 20:18:03 UTC

Parallelism

80/100

Blocked

36%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,606,102  ·  15 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

6 touches
3 conflicts

0x1b36ca9b…6a67

0x065c9d…c394

5 touches
3 conflicts

0xe90b7bce…c2e0

0xfa32f9…f3f0

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

4 touches
1 conflict

0x9194f4a3…10b8

0x754704…b603

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xffe004da…e2f4

0x754704…b603

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

3 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity