← previous blocknext block →recent activity

Analyzing

Block #74,722,189

15 transactions · 13 stateful · 2026-05-15 09:12:07 UTC

Parallelism

73/100

Blocked

38%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,722,189  ·  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

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xa05dafe7…aff6

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0004

0x5afd3e…7620

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

4 touches
1 conflict

0x84fb2a36…db89

0x34b655…2a6f

4 touches
1 conflict

0xded5ec0c…f0fc

0x34b655…2a6f

4 touches
1 conflict

0xe5e7089a…fb91

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: 0x34b6552d…112a6f

3 conflicts on slot 0x8c49c85c3e…afee96

← previous block·next block →recent activity