← previous blocknext block →recent activity

Analyzing

Block #75,247,046

10 transactions · 6 stateful · 2026-05-17 19:37:28 UTC

Parallelism

80/100

Blocked

33%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #75,247,046  ·  10 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

0xfe2bac2b…2cec

0x065c9d…c394

4 touches
1 conflict

0xf3d7a307…4d63

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x9b091d85…037c

0x065c9d…c394

3 touches
1 conflict

0xfe35b597…216f

0x065c9d…c394

3 touches
1 conflict

0xeeb06c54…c920

0x065c9d…c394

3 touches
1 conflict

0x5dbf0f23…e76a

0x065c9d…c394

3 touches
1 conflict

0x00000000…001b

0x1b6862…e19c

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 0xfe2bac2b2f…482cec

← previous block·next block →recent activity