← previous blocknext block →recent activity

Analyzing

Block #74,734,086

7 transactions · 7 stateful · 2026-05-15 10:31:50 UTC

Parallelism

71/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,734,086  ·  7 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

0x70d3da25…080e

0x065c9d…c394

4 touches
1 conflict

0xf3d7a307…4d63

0x065c9d…c394

4 touches
1 conflict

0x9ba2a4f6…f8fd

0x065c9d…c394

3 touches
1 conflict

0x9ebb9514…a117

0x065c9d…c394

3 touches
1 conflict

0xfe2bac2b…2cec

0x065c9d…c394

2 touches
0 conflicts

0x30276c1c…47b4

0x2a68ba…90c5

2 touches
0 conflicts

0x765c236f…ff45

0x2a68ba…90c5

2 touches
0 conflicts

0x00000000…0004

0x35fa64…a655

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 0x70d3da25b3…bc080e

← previous block·next block →recent activity