← previous blocknext block →recent activity

Analyzing

Block #74,284,172

22 transactions · 18 stateful · 2026-05-13 08:28:00 UTC

Parallelism

73/100

Blocked

44%

Avg conflicts / tx

0.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,284,172  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x1efdd4d7…daa3

0xd32edf…ff58

11 touches
15 conflicts

0xf823e97f…2ee6

0x065c9d…c394

4 touches
1 conflict

0x76143714…af47

0x065c9d…c394

4 touches
1 conflict

0x4d227e47…e6b1

0x34b655…2a6f

4 touches
1 conflict

0xb9d2cf20…a668

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xfa2527aa…9dd5

0x34b655…2a6f

4 touches
1 conflict

0xc12b04b0…884b

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: 0xd32edf66…9fff58

15 conflicts on slot 0x1efdd4d769…b6daa3

← previous block·next block →recent activity