← previous blocknext block →recent activity

Analyzing

Block #74,331,493

28 transactions · 22 stateful · 2026-05-13 13:42:49 UTC

Parallelism

82/100

Blocked

50%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #74,331,493  ·  28 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8c8d0f3a…7d68

0xd32edf…ff58

7 touches
6 conflicts

0xf3981be5…2c47

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1a6

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1a7

0x8d66a4…3095

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xd59f6ed1…03e5

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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

6 conflicts on slot 0x8c8d0f3aa5…c77d68

← previous block·next block →recent activity