← previous blocknext block →recent activity

Analyzing

Block #74,770,929

18 transactions · 11 stateful · 2026-05-15 14:38:18 UTC

Parallelism

83/100

Blocked

36%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,770,929  ·  18 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

0x00000000…0002

0xab3526…fa38

6 touches
3 conflicts

0xba38536d…2b7d

0x065c9d…c394

4 touches
1 conflict

0x202d612e…219a

0x065c9d…c394

4 touches
1 conflict

0x426cf25c…8e39

0x065c9d…c394

3 touches
1 conflict

0xc6248f6a…7008

0x065c9d…c394

3 touches
1 conflict

0x39b7c3a7…0b72

0x065c9d…c394

2 touches
0 conflicts

0xd23698ed…0cb3

0x065c9d…c394

2 touches
0 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

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

3 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity