← previous blocknext block →recent activity

Analyzing

Block #74,738,664

17 transactions · 15 stateful · 2026-05-15 11:02:15 UTC

Parallelism

76/100

Blocked

27%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #74,738,664  ·  17 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…003d

0x065c9d…c394

8 touches
6 conflicts

0xf3d7a307…4d63

0x065c9d…c394

4 touches
1 conflict

0x602a6094…0644

0x34b655…2a6f

4 touches
1 conflict

0x801a6e57…d85c

0x34b655…2a6f

4 touches
1 conflict

0xd32847a2…901e

0x065c9d…c394

3 touches
1 conflict

0x964f809c…1c46

0x065c9d…c394

2 touches
0 conflicts

0xac42e8ce…e884

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity