← previous blocknext block →recent activity

Analyzing

Block #74,284,026

17 transactions · 13 stateful · 2026-05-13 08:27:01 UTC

Parallelism

82/100

Blocked

31%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,284,026  ·  17 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

0x335a161d…fe7f

0x000000…012a

6 touches
3 conflicts

0xdd967976…5491

0x699abc…6a3b

6 touches
3 conflicts

0x6bfffdcd…7d7b

0x699abc…6a3b

5 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xb9d2cf20…a668

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0x7084519d…e0a1

0x34b655…2a6f

4 touches
1 conflict

0x0dfa19df…1586

0xd32edf…ff58

3 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: 0x00000000…a9012a

3 conflicts on slot 0x335a161d76…bdfe7f

← previous block·next block →recent activity