← previous blocknext block →recent activity

Analyzing

Block #74,596,557

15 transactions · 11 stateful · 2026-05-14 19:13:49 UTC

Parallelism

73/100

Blocked

27%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,596,557  ·  15 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x00000000…0004

0x8d66a4…3095

8 touches
6 conflicts

0xa94cf3f4…554c

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1a6

0x8d66a4…3095

6 touches
3 conflicts

0xfff38d9f…7063

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1a7

0x8d66a4…3095

5 touches
3 conflicts

0x8a35acfb…d1a1

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a5

0x8d66a4…3095

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

6 conflicts on slot 0x60f7fbaf90…97bd58

← previous block·next block →recent activity