← previous blocknext block →recent activity

Analyzing

Block #74,594,051

16 transactions · 14 stateful · 2026-05-14 18:57:01 UTC

Parallelism

56/100

Blocked

50%

Avg conflicts / tx

1.38

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,594,051  ·  16 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0x1686502b…a1d2

0x3bd359…433a

4 touches
1 conflict

0x00000000…0001

0x86dfd5…6a7d

4 touches
1 conflict

0x1d4c90ab…1ba7

0xb72e62…7777

4 touches
1 conflict

0x44ad89ba…cf83

0xb72e62…7777

4 touches
1 conflict

0x00000000…0000

0x86dfd5…6a7d

4 touches
1 conflict

0x0fc41e7b…6831

0x98dc6e…8633

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

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity