← previous blocknext block →recent activity

Analyzing

Block #74,766,842

14 transactions · 8 stateful · 2026-05-15 14:10:54 UTC

Parallelism

86/100

Blocked

13%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,766,842  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x443a3e47…f4a4

0x065c9d…c394

4 touches
1 conflict

0x84a759fb…65d4

0x065c9d…c394

4 touches
1 conflict

0x7bbe5bd8…753c

0x065c9d…c394

3 touches
1 conflict

0xa973fbe6…2795

0x065c9d…c394

3 touches
1 conflict

0xbf50a329…c8ff

0x065c9d…c394

3 touches
1 conflict

0xfcb7b8b2…ebb3

0x065c9d…c394

2 touches
0 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

2 touches
0 conflicts

0x438cf5f6…f077

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: 0x065c9d28…a9c394

1 conflict on slot 0x443a3e479f…3af4a4

← previous block·next block →recent activity