← previous blocknext block →recent activity

Analyzing

Block #74,332,582

17 transactions · 11 stateful · 2026-05-13 13:50:03 UTC

Parallelism

76/100

Blocked

45%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,332,582  ·  17 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

0x00000000…0002

0xab3526…fa38

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x17cd1479…00bb

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d19c

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a5

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a6

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1a7

0x8d66a4…3095

4 touches
1 conflict

0x9d1bb389…c7d9

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: 0xab35264b…1cfa38

6 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity