← previous blocknext block →recent activity

Analyzing

Block #74,355,825

18 transactions · 13 stateful · 2026-05-13 16:24:36 UTC

Parallelism

78/100

Blocked

31%

Avg conflicts / tx

0.44

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,355,825  ·  18 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0xa56a84d2…0dcd

0x000000…a032

2 touches
0 conflicts

0x41755291…977f

0x065c9d…c394

2 touches
0 conflicts

0xb908898f…96c7

0x065c9d…c394

2 touches
0 conflicts

0xdeacdf74…4120

0x065c9d…c394

2 touches
0 conflicts

0xe063b94e…3a0a

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

6 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity