← previous blocknext block →recent activity

Analyzing

Block #74,402,845

22 transactions · 14 stateful · 2026-05-13 21:37:37 UTC

Parallelism

86/100

Blocked

36%

Avg conflicts / tx

0.32

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,402,845  ·  22 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

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xc684c7fc…0547

0x34b655…2a6f

4 touches
1 conflict

0xa486f342…64d5

0x34b655…2a6f

4 touches
1 conflict

0xb245fe36…d765

0x34b655…2a6f

4 touches
1 conflict

0xd5ad0af4…2387

0x34b655…2a6f

4 touches
1 conflict

0x95e5ee51…5e3e

0x34b655…2a6f

2 touches
0 conflicts

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