← previous blocknext block →recent activity

Analyzing

Block #74,332,373

21 transactions · 14 stateful · 2026-05-13 13:48:39 UTC

Parallelism

81/100

Blocked

36%

Avg conflicts / tx

0.24

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,332,373  ·  21 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

0x8a35acfb…d19f

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a4

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a9

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1aa

0x8d66a4…3095

4 touches
1 conflict

0xa94cf3f4…554c

0x8d66a4…3095

4 touches
1 conflict

0xfff38d9f…7063

0x8d66a4…3095

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x60f7fbaf…bd58

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: 0x8d66a43f…113095

1 conflict on slot 0x8a35acfbc1…6bd19f

← previous block·next block →recent activity