← previous blocknext block →recent activity

Analyzing

Block #74,346,764

14 transactions · 12 stateful · 2026-05-13 15:24:24 UTC

Parallelism

79/100

Blocked

25%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,346,764  ·  14 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

0x1c389468…6b0e

0x34b655…2a6f

6 touches
3 conflicts

0xebd4e235…6945

0x8d66a4…3095

4 touches
1 conflict

0x74825c4e…32e9

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d19f

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a8

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a9

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1aa

0x8d66a4…3095

4 touches
1 conflict

0xcc6521c1…c892

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

3 conflicts on slot 0x1c38946843…a16b0e

← previous block·next block →recent activity