← previous blocknext block →recent activity

Analyzing

Block #74,727,203

27 transactions · 24 stateful · 2026-05-15 09:45:46 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

1.15

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,727,203  ·  27 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

16 touches
28 conflicts

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x00000000…0000

0xd92cf7…0465

4 touches
1 conflict

0x7b31453a…f4c1

0x065c9d…c394

2 touches
0 conflicts

0xbcd06717…bfb7

0x065c9d…c394

2 touches
0 conflicts

0xd4a0f0bd…dae6

0x065c9d…c394

2 touches
0 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

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

28 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity